{
  "phase_id": "phase-02",
  "category_id": "architecture_engineering_core",
  "doc_id": "acs",
  "source_path": "/home/yeff/public_html/devon/panel/data/acs.md",
  "documentation_branch_status": "CUSTOM_BRANCH",
  "bucket_statuses_from_docs_index": {
    "Prerequisites": "ACTIVE",
    "Installation": "ACTIVE",
    "Configuration": "ACTIVE",
    "Validation": "ACTIVE",
    "Observable Evidence": "ACTIVE",
    "Failure Modes & Recovery": "ACTIVE",
    "Completion & Promotion": "ACTIVE"
  },
  "exported_at": "2026-04-28T05:56:48.644291+00:00",
  "export_rule": "docs/json export generated from real panel/data source plus docs/index.php branch evidence; no authored content invented by export patch",
  "source_payload": {
    "source_format": "markdown",
    "raw_markdown": "# ACS — ARTIFACT CANON SPEC\nversion: v1.0\nstatus: ACTIVE\nparent: master_architecture_index.md\nphase: 02\nphase_name: Architecture & Engineering Canon\ndocument_role: artifact_canon_standard_for_phase_02\n\n---\n\n## 1. OBJECTIVE\n\nDefine where canonical artifacts live, how they are classified, and how they relate to governance, runtime, UI and operational flows.\n\n---\n\n## 2. ARTIFACT CLASSES\n\nCanonical artifact classes:\n- governance_spec\n- architecture_spec\n- security_spec\n- performance_spec\n- observability_spec\n- flow_spec\n- runtime_contract\n- registry\n- canonical_json\n- ui_mapping\n- audit_evidence\n\n---\n\n## 3. CANONICAL ROOT\n\nPrimary canonical root:\n`/home/yeff/public_html/devon/panel/data/`\n\nPrimary master reference:\n`/home/yeff/public_html/devon/panel/data/master_architecture_index.md`\n\n---\n\n## 4. PLACEMENT RULE\n\nArtifacts that govern architecture, execution, contracts or panel structure must live under `panel/data`.\n\nArtifacts must not be scattered across unrelated folders without canon update.\n\n---\n\n## 5. SOURCE OF TRUTH RULE\n\nAuthority order:\n1. master_architecture_index.md\n2. canonical json roots\n3. canonical md specs\n4. phase-specific specs\n5. OFS files\n6. UI mapping layer\n\nLower layers must not contradict upper layers.\n\n---\n\n## 6. ARTIFACT METADATA\n\nEvery canonical artifact must expose:\n- identity\n- role\n- phase\n- parent\n- status\n- purpose\n- traceability target\n\n---\n\n## 7. TRACEABILITY RULE\n\nEvery UI-facing label, runtime contract or flow reference must resolve back to one canonical artifact.\n\nNo orphan artifact allowed.\n\n---\n\n## 8. ACCEPTANCE CRITERIA\n\nACS is valid only if:\n- canonical root is explicit\n- artifact classes are explicit\n- authority order is explicit\n- placement rule is explicit\n- traceability rule is explicit\n"
  }
}