Skip to main content
Version: v0.1.73

Project Standards

Project Standards are org-defined checks that your projects and assets are expected to satisfy — a naming convention, a required tag, a documentation-completeness bar, a certification prerequisite. Where Governance gates a single promote-to-live and Data Quality watches the data, Project Standards watch the project against organization policy and produce a compliance report.

The org check library​

Standards are authored once in an org check library and reused across projects — you don't re-declare "every dashboard must have a description" per project. A check names what it inspects and the condition it expects; the library is the single source of truth an admin curates.

Scopes​

Each check declares an ordered list of scopes — which assets and projects it applies to (for example: all dashboards, or only projects in a given stage). Scopes are evaluated in order, so a broad default can be narrowed by a more specific scope. A check only runs where its scope matches.

Severity and the compliance report​

A check carries a severity on a 0–5 scale, from informational up to blocking. Running the standards produces a compliance report: per-check, which assets pass and which fail, rolled up by severity so a reviewer sees the blocking failures first and the advisory ones last. The report is the artifact a governance owner reads to answer "is this project up to standard?"

How it runs​

Standards evaluate against the org's assets and write their results to the standards tables (standards_*). Because the results are keyed by org, an install with several tenants keeps each tenant's compliance report isolated.

  • Governance — the automated review checks that gate an individual promote-to-live.
  • The Asset Registry — the fleet view of agents/dashboards/webapps with lifecycle stage, owner, and certification, where standards compliance surfaces per asset.
  • The Enterprise Asset Library — reusable code / prompt / card templates an org publishes for teams to instantiate, so new assets start compliant.

Permissions​

Authoring and running standards is an administrative surface (org.admin). Compliance results are readable by anyone who can see the assets they cover.

See also​