{
  "id": "page:process-03-governance",
  "_kind": "Page",
  "_file": "wiki/process/03-governance.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "title": "Governance",
    "displayName": "Governance",
    "slug": "process/03-governance",
    "articlePath": "wiki/process/03-governance.md",
    "article": "# Governance\n\n> Companion to [`00-process-design.md`](./00-process-design.md), Section 8.\n\nEvery phase and every debt-loop level has a named owner. Owners are represented as `Authority` nodes in the graph and referenced from the `owner` field on `Gap` nodes (and on `Claim`, `EvidenceSource` per the evidence model).\n\n## Per-phase owners\n\n| Phase | Owner role | Responsibilities |\n|---|---|---|\n| 1 — Schema | **Schema owner** | Final say on `ontology-schema.yaml`, `attribute-types.yaml`, `invariants.yaml`, the meta-schema, and all `02-node-kinds/` specs. Approves schema bumps. |\n| 2 — Full graph | **Graph data owners** (one per cluster group) | Drive full-coverage population for their NodeKinds. Sign off on evidence freshness. |\n| 3 — Generators | **Generator owners** (one per generator listed in `06-derivation-spec.md`, plus the `Gap` sync generator) | Maintain the generator code, templates, and integration tests. |\n| 4 — Wiki | **Wiki editors** | Navigation, search, page templates, asset handling. Page **content** is generated; editors do not author prose. |\n| 5 — QA / delivery | **QA owner** | CI/CD pipeline, evidence-boundary checks, release gates, downstream artifact distribution, versioning enforcement. |\n\n## Per-level owners (debt loop)\n\n| Level | Owner |\n|---|---|\n| 1 — Real world vs graph | **Debt-loop coordinator** runs the weekly batch review; cluster-specific graph data owners execute. |\n| 2 — Graph vs docs | Schema owner (gate at PR) + relevant graph data owner (fix). |\n| 3 — Process docs | Debt-loop coordinator. |\n| 4 — Generators / wiki | Generator owner of the affected generator + wiki editor for navigation impact. |\n| 5 — Code vs docs | Generator owner (for generator code) or QA owner (for validators / runtime helpers). |\n| 6 — SDK | QA owner (releases) + schema owner (contract). |\n| 7 — Interfaces | The owner of each interface (CLI, dashboard, etc.) — recorded as the `Authority` on the relevant `Presentation` node. |\n\n## Cross-cutting\n\nThe **debt-loop coordinator** is responsible for ensuring the cascade rule ([`02-cascade-rule.md`](./02-cascade-rule.md)) is applied on every gap closure, runs the weekly Level-1 batch review, and arbitrates priority disputes. They do **not** approve their own work — the adversarial-review rule (Section 5) still applies.\n\nWhen two graph data owners disagree on a cross-cluster edge, the **schema owner** arbitrates. When schema and QA owners disagree on a release gate, the debt-loop coordinator brokers. All such arbitration outcomes land as `Gap` resolutions with `propagationChain` entries citing the deciding authority.\n\nHuman-in-the-loop is required for schema changes (any edit to `ontology-schema.yaml`, `attribute-types.yaml`, or `invariants.yaml`); agent-only review is sufficient for graph data changes that do not bump the schema.\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:process",
      "to": "page:process-03-governance",
      "kind": "contains_page"
    }
  ]
}