{
  "phase_id": "phase-02",
  "category_id": "architecture_engineering_core",
  "doc_id": "css",
  "source_path": "/home/yeff/public_html/devon/panel/data/css.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": "# CSS — CONTRACT & SCHEMA SPEC\nversion: v1.0\nstatus: ACTIVE\nparent: master_architecture_index.md\nphase: 02\nphase_name: Architecture & Engineering Canon\ndocument_role: contract_and_schema_standard_for_phase_02\n\n---\n\n## 1. OBJECTIVE\n\nDefine how Devon contracts and schemas must be structured.\n\n---\n\n## 2. CONTRACT PRINCIPLE\n\nEvery meaningful interface must be contract-bound.\n\nContracts apply to:\n- module input\n- module output\n- runtime bridge\n- panel data\n- memory writes\n- validation outputs\n- execution payloads\n\nAudit surface rule:\n- documentation-facing structures may summarize canonical definitions\n- operational-facing structures may expose real runtime evidence\n- no contract may blur documentary summary with operational proof\n\n---\n\n## 3. REQUIRED CONTRACT ELEMENTS\n\nEach contract should define:\n- identity\n- purpose\n- required fields\n- allowed values\n- forbidden values when relevant\n- validation expectation\n- failure semantics\n\n---\n\n## 4. SCHEMA PRINCIPLE\n\nSchemas must prefer:\n- explicit fields\n- deterministic validation\n- traceable identifiers\n- versioned structures\n\nNo vague payloads allowed for governed operations.\n\n---\n\n## 5. ACCEPTANCE CRITERIA\n\nCSS is valid only if:\n- contract fields are explicit\n- schema rule is explicit\n- failure semantics are explicit\n- governed interfaces are covered\n"
  }
}