{
  "phase_id": "phase-02",
  "category_id": "architecture_engineering_core",
  "doc_id": "ncs",
  "source_path": "/home/yeff/public_html/devon/panel/data/ncs.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": "# NCS — NAMING & CONTRACT SPEC\nversion: v1.0\nstatus: ACTIVE\nparent: master_architecture_index.md\nphase: 02\nphase_name: Architecture & Engineering Canon\ndocument_role: naming_and_contract_standard_for_phase_02\n\n---\n\n## 1. OBJECTIVE\n\nDefine canonical naming rules for Devon architecture, documentation, runtime artifacts, panel data, phases, contracts and operational identifiers.\n\nThis document standardizes:\n- file names\n- document siglas\n- canonical IDs\n- phase labels\n- card IDs\n- section IDs\n- path conventions\n- contract naming patterns\n\n---\n\n## 2. NAMING PRINCIPLE\n\nEvery canonical artifact must be:\n- explicit\n- stable\n- singular in responsibility\n- machine-readable\n- human-readable\n- traceable to phase and role\n\nNo decorative naming allowed.\nNo vague naming allowed.\nNo duplicate purpose naming allowed.\n\n---\n\n## 3. FILE NAMING RULES\n\n### 3.1 Canonical Data Files\nCanonical structured files must use:\n\n`snake_case.json`\n\nExamples:\n- project_scope_canonical.json\n- deployment_order_canonical.json\n- panel_canonical_tree.json\n- server_registry_canonical.json\n\n### 3.2 Canonical Markdown Files\nCanonical textual governance/spec files must use:\n\n`lowercase_sigla.md`\n\nExamples:\n- cgs.md\n- ncs.md\n- acs.md\n- cas.md\n- ris.md\n\n### 3.3 Forbidden Patterns\nForbidden:\n- spaces in file names\n- camelCase file names\n- mixed separators\n- decorative suffixes\n- vague names like:\n  - final_doc.md\n  - new_version.md\n  - temp_file.md\n  - architecture_notes.md\n\n---\n\n## 4. DOCUMENT SIGLA RULES\n\nEvery canonical spec must have:\n- a unique sigla\n- one sigla = one responsibility\n- no sigla reuse\n\nExamples:\n- CGS = Canonical Governance Spec\n- NCS = Naming & Contract Spec\n- ACS = Artifact Canon Spec\n- CAS = Cognitive Architecture Spec\n- RIS = Role Isolation Spec\n- STS = State & Transition Spec\n- OFMS = Operational Flow Master Spec\n- CDMS = Containerization & Deployment Master Spec\n- CSS = Contract & Schema Spec\n- BRPS = Build, Release & Promotion Spec\n\n---\n\n## 5. PATH RULES\n\n### 5.1 Canonical Root\nCanonical architecture reference root:\n\n`/home/yeff/public_html/devon/panel/data/`\n\n### 5.2 Master Reference\nPrimary consultation file:\n\n`/home/yeff/public_html/devon/panel/data/master_architecture_index.md`\n\n### 5.3 Rule\nCanonical docs that govern panel, architecture or execution must live under:\n- panel/data\n\nUnless a higher canon explicitly defines another root.\n\n---\n\n## 6. PHASE NAMING RULES\n\nOfficial phase names:\n\n- Phase 01 — Overview & Scope\n- Phase 02 — Architecture & Engineering Canon\n- Phase 03 — Foundations Security\n- Phase 04 — Performance, Observability & Quality\n- Phase 05 — Architecture\n- Phase 06 — Contracts\n- Phase 07 — Runtime & Infrastructure\n- Phase 08 — Memory & Learning\n- Phase 09 — Operational Flows\n\n### 6.1 Phase ID Format\nUse:\n- `phase: 02`\n- `phase_name: Architecture & Engineering Canon`\n\n### 6.2 Forbidden\nDo not use:\n- informal aliases as authority\n- multiple names for same phase\n- reordered numbering without canon update\n\n---\n\n## 7. DOCUMENT HEADER CONTRACT\n\nEvery canonical md spec must declare:\n\n- title\n- version\n- status\n- parent\n- phase\n- phase_name\n- document_role\n\nExample:\n\n```text\n# CGS — CANONICAL GOVERNANCE SPEC\nversion: v1.0\nstatus: ACTIVE\nparent: master_architecture_index.md\nphase: 02\nphase_name: Architecture & Engineering Canon\ndocument_role: governance_root_for_phase_02\n"
  }
}