{ "phases": [ { "id": "phase-01", "step": "Phase 01", "name": "Overview & Scope", "summary": "master root, project scope, manifest and continuity checkpoint.", "badge": "overview_scope", "layers": [ { "title": "Overview & Scope", "desc": "master registration, project framing, entry manifest and continuity checkpoint.", "chips": [ "master root", "project scope", "entry manifest", "checkpoint" ] } ] }, { "id": "phase-02", "step": "Phase 02", "name": "Architecture & Engineering Canon", "summary": "cognitive architecture, governance, artifact structure, contracts, naming, state legitimacy, build promotion, deployment structure and contextual satellites.", "badge": "architecture_engineering_canon", "layers": [ { "title": "Architecture & Engineering Canon", "desc": "authority and satellite documents that define Devon structural canon.", "chips": [ "architecture", "governance", "contracts", "naming", "state legitimacy", "deployment" ] } ] }, { "id": "phase-03", "step": "Phase 03", "name": "Cognitive Flow Canon", "summary": "deterministic orchestration, LLM role, retrieval role, validation order and execution gating.", "badge": "cognitive_flow_canon", "layers": [ { "title": "Cognitive Flow Canon", "desc": "interpreter, decision, validation, execution, memory and retrieval in governed flow.", "chips": [ "interpreter", "FSM", "validation", "execution", "memory", "retrieval" ] } ] }, { "id": "phase-04", "step": "Phase 04", "name": "Containerization Canon", "summary": "container topology, isolation and host versus container runtime boundaries.", "badge": "containerization_canon", "layers": [ { "title": "Containerization Canon", "desc": "runtime boundaries and isolation, without redefining sovereign architecture.", "chips": [ "topology", "isolation", "runtime boundaries" ] } ] }, { "id": "phase-05", "step": "Phase 05", "name": "Latency & Performance Canon", "summary": "latency model, hot path versus cold path, bounded execution and fallback behavior.", "badge": "latency_performance_canon", "layers": [ { "title": "Latency & Performance Canon", "desc": "time traceability across modules, stages and end-to-end lifecycle.", "chips": [ "latency", "hot path", "cold path", "fallback" ] } ] }, { "id": "phase-06", "step": "Phase 06", "name": "Noise Reduction Canon", "summary": "signal preservation, redundancy elimination and unnecessary hop reduction.", "badge": "noise_reduction_canon", "layers": [ { "title": "Noise Reduction Canon", "desc": "remove architectural waste and keep deterministic path lean.", "chips": [ "signal", "redundancy elimination", "less path" ] } ] }, { "id": "phase-07", "step": "Phase 07", "name": "Observability & Audit Canon", "summary": "audit-linked visibility, evidence continuity and operational observability.", "badge": "observability_audit_canon", "layers": [ { "title": "Observability & Audit Canon", "desc": "traceability for runtime, memory and protected execution.", "chips": [ "observability", "audit", "evidence continuity" ] } ] }, { "id": "phase-08", "step": "Phase 08", "name": "Security Canon", "summary": "security governance, trust model, access boundaries, memory protection and monitoring.", "badge": "security_canon", "layers": [ { "title": "Security Canon", "desc": "security governance with structured implementation artifacts.", "chips": [ "zero trust", "access control", "memory protection", "monitoring" ] } ] }, { "id": "phase-09", "step": "Phase 09", "name": "Operational Flows Canon", "summary": "execution sequence, operating flow mapping and operational order integrity.", "badge": "operational_flows_canon", "layers": [ { "title": "Operational Flows Canon", "desc": "runtime sequence and flow order without redefining sovereign authorities.", "chips": [ "operational flow", "sequence", "order integrity" ] } ] }, { "id": "phase-10", "step": "Phase 10", "name": "Monitoring & Real-time Observability", "summary": "real-time host, container and service monitoring with SSE transport to the Operator Panel.", "badge": "monitoring_observability", "layers": [ { "title": "Monitoring & Real-time Observability", "desc": "CPU, memory, disk, network, container health, security services and SSE bridge canon.", "chips": [ "cpu", "memory", "containers", "network", "security", "SSE" ] } ] } ], "categories": [ { "id": "overview_scope", "title": "Overview & Scope", "sub": "master registration, project scope, manifest and continuity checkpoint.", "badge": "phase 01", "docs": [ { "id": "master_architecture_index", "title": "Master Architecture Index", "path": "../panel/data/master_architecture_index.md", "phase": "phase-01", "layer": "overview_scope", "role": "Supreme canonical root and registration authority.", "fits": "Defines registration, precedence, authority ownership and completeness rules.", "depends_on": [ "panel_manifest", "project_scope" ], "used_by": [], "architecture_view": "Supreme human-readable root for all Devon canon.", "label": "Master Architecture Index", "type": "text" }, { "id": "panel_manifest", "title": "Panel Manifest", "path": "../panel/data/panel_manifest.json", "phase": "phase-01", "layer": "overview_scope", "role": "Entry manifest and machine-readable panel entry point.", "fits": "Belongs to project overview and registration surface.", "depends_on": [ "master_architecture_index" ], "used_by": [], "architecture_view": "Entry manifest for the panel and documentation surface.", "label": "Panel Manifest", "type": "json" }, { "id": "project_scope", "title": "Project Scope Canonical", "path": "../panel/data/project_scope_canonical.json", "phase": "phase-01", "layer": "overview_scope", "role": "Machine-readable project scope authority.", "fits": "Defines project framing and scope surface.", "depends_on": [ "master_architecture_index" ], "used_by": [], "architecture_view": "Scope anchor for the project overview.", "label": "Project Scope Canonical", "type": "json" }, { "id": "deployment_order", "title": "Deployment Order Canonical", "path": "../panel/data/deployment_order_canonical.json", "phase": "phase-01", "layer": "overview_scope", "role": "Machine-readable deployment order authority.", "fits": "Defines canonical installation and configuration order.", "depends_on": [ "master_architecture_index" ], "used_by": [], "architecture_view": "Deployment order reference.", "label": "Deployment Order Canonical", "type": "json" }, { "id": "sandbox_environment", "title": "Sandbox Environment Canonical", "path": "../panel/data/sandbox_environment_canonical.json", "phase": "phase-01", "layer": "overview_scope", "role": "Machine-readable sandbox environment authority.", "fits": "Defines sandbox execution boundaries and environment expectations.", "depends_on": [ "master_architecture_index" ], "used_by": [], "architecture_view": "Sandbox boundary reference.", "label": "Sandbox Environment Canonical", "type": "json" }, { "id": "server_registry", "title": "Server Registry Canonical", "path": "../panel/data/server_registry_canonical.json", "phase": "phase-01", "layer": "overview_scope", "role": "Machine-readable server registry authority.", "fits": "Defines canonical server identities and registry surface.", "depends_on": [ "master_architecture_index" ], "used_by": [], "architecture_view": "Server registry reference.", "label": "Server Registry Canonical", "type": "json" }, { "id": "project_progress_canonical", "title": "Project Progress Canonical", "path": "../panel/data/project_progress_canonical.json", "phase": "phase-01", "layer": "overview_scope", "role": "Sovereign canonical model for global project progress calculation.", "fits": "Defines the only valid calculation mode and required fields for global progress.", "depends_on": [ "master_architecture_index" ], "used_by": [ "project_progress_model" ], "architecture_view": "Global progress canonical authority.", "label": "Project Progress Canonical", "type": "json" }, { "id": "project_progress_model", "title": "Project Progress Model", "path": "../panel/data/project_progress_model.json", "phase": "phase-01", "layer": "overview_scope", "role": "Sovereign stage weighting model for global project progress.", "fits": "Defines explicit weights per stage for the global progress donut.", "depends_on": [ "project_progress_canonical", "master_architecture_index" ], "used_by": [], "architecture_view": "Stage weight authority for global progress.", "label": "Project Progress Model", "type": "json" } ], "phase_id": "phase-01", "subcategories": [ { "id": "prerequisites", "label": "prerequisites", "status": "ACTIVE", "buckets": [ { "title": "Purpose", "items": [ "Define the mandatory preconditions that must exist before Devon can be considered structurally valid as a canonical program, not merely as an isolated UI, host or runtime implementation.", "Answer without ambiguity what must exist before downstream phases can be trusted, why each prerequisite exists, which phase boundary it belongs to, which authority artifact governs it, which supporting artifacts operationalize it, which dependency chain it unlocks, and how Documentation Hub and Operator Panel must project it downstream.", "Treat the prerequisite model as program-wide, covering the full path from canonical registration and deployment order through architecture, runtime publication, trust controls, memory governance and monitoring exposure." ] }, { "title": "Sovereign rule", "items": [ "No downstream phase may be treated as structurally valid unless its upstream prerequisites are materially registered, bounded by authority, and observable through the canonical roots.", "Mandatory root split: panel/data = system state, contracts, schemas, DH bridge, runtime and support artifacts.", "Mandatory root split: canon = operational governance, rules, decisions, scope and continuity.", "Both roots are mandatory and may not be collapsed into a single mixed source of truth." ] }, { "title": "Prerequisite classification model", "items": [ "Canon prerequisites: these define whether the project is canonically registered and structurally governable.", "Canon prerequisites require a sovereign root reference, explicit file ownership and precedence, one concept = one primary authority, explicit phase/category/subcategory organization, and unambiguous deployment and reading order.", "Operational prerequisites: these define whether the project can be executed under the Devon operating law.", "Operational prerequisites require mandatory context reconstruction, no analysis without dump, no patch without dump, observable evidence before validation, and status restricted to PASS / FAIL / MISSING / PLANNED.", "Infrastructure prerequisites: these define whether the host and deployment substrate materially exist.", "Infrastructure prerequisites require an observable Devon host baseline, material base tooling, bounded security/network baseline, and explicit declaration of missing infrastructure as MISSING.", "Publication prerequisites: these define whether Devon can publish machine-readable truth to downstream consumers.", "Publication prerequisites require canonical runtime contracts, a publication bridge, contract-bounded exported runtime artifacts, and downstream UI consumption of published truth instead of local invention.", "Projection prerequisites: these define whether the Documentation Hub and Operator Panel are allowed to project the canon.", "Projection prerequisites require DH to project category/document authority correctly, Panel to read declared semantics correctly, navigation to preserve Phase -> Category, center workflow to preserve Subcategory -> Bucket -> Item, and no layer abstraction replacing documentary ownership." ] }, { "title": "Global project prerequisites", "items": [ "P01. Canonical root registration: Devon must have a sovereign architectural root that registers canonical existence, role, precedence, ownership and dependency mapping.", "P01 unlocks phase registration, category ownership, DH navigation integrity and downstream artifact legitimacy.", "P02. Source-of-truth separation: the project must preserve the hard split between governance and system state.", "P02 unlocks clean governance, safe DH projection, safe Panel consumption and conflict resolution.", "P03. Evidence-first operating law: all work must start from server evidence, never from chat memory.", "P03 requires /home/yeff/public_html/devon/context_dump.sh before analysis and patch generation, and unlocks valid diagnostics, valid status attribution and continuity integrity.", "P04. Global status model: every prerequisite must resolve into PASS, FAIL, MISSING or PLANNED.", "P04 unlocks deterministic validation, non-fictional progress reporting and project-wide boolean reading.", "P05. Structural organization model: the project must be organized through Phase, Category, Subcategory and installation / configuration order.", "P05 unlocks DH structure, category authority mapping and predictable downstream rendering." ] }, { "title": "Cross-phase prerequisites", "items": [ "P06. Deployment order must exist before expansion.", "P06 unlocks phase gating, dependency sequencing and non-chaotic implementation.", "P07. Authority ownership must exist before category materialization.", "P07 requires each phase/category to be bound to a sovereign authority document or tightly bounded documentary group, and unlocks category legitimacy, DH item binding and traceable document authority.", "P08. Contract artifacts must exist before runtime/UI truth claims.", "P08 requires runtime_expected_manifest.json, runtime_probe_registry.json, build_runtime_contracts.py, runtime_row_semantics_canonical.json, project_progress_canonical.json and project_progress_model.json, and unlocks trustworthy progress, stage-level reading and semantic completion logic.", "P09. Publication bridge must exist before downstream projection is trusted.", "P09 requires export_panel_runtime.sh and published artifacts such as runtime_snapshot.json, runtime_status.json, host_runtime.json, docker_runtime.json and project_progress.json, and unlocks real runtime visibility, panel synchronization and DH / Panel downstream consistency.", "P10. Semantic reading rules must exist before completion is shown.", "P10 requires deployment_stage, subcategory, row_kind, semantic_scope, counts_toward_completion, display_in_cards, display_in_donuts, ui_group and source_contract, and unlocks valid donuts, valid stage rollups and non-corrupt progress presentation." ] }, { "title": "Infrastructure and environment prerequisites", "items": [ "P11. Host baseline must be observable.", "P11 observed baseline includes Ubuntu 22.04.5 LTS, Linux 5.15.0-170-generic, x86-64, 6 vCPU, 11 GiB RAM, 100 GB disk and SSH exposed on port 22 only.", "P11 unlocks installation planning, security hardening and runtime deployment feasibility.", "P12. Security baseline must be bounded.", "P12 observed conditions include firewall active, UFW deny incoming / allow outgoing, inbound rule 22/tcp and iptables INPUT DROP / FORWARD DROP / OUTPUT ACCEPT.", "P12 observed missing conditions include reverse proxy = MISSING and TLS baseline = MISSING.", "P12 unlocks trusted service exposure, future publication hardening and runtime trust boundary expansion.", "P13. Base tooling must exist materially.", "P13 observed present tooling includes Python3, Git and Curl; observed missing tooling includes Docker, Docker Compose and Nginx.", "P13 unlocks container runtime, service publication, reverse proxy layer and operational packaging." ] }, { "title": "Documentation Hub and Operator Panel prerequisites", "items": [ "P14. Documentation Hub must preserve documentary authority.", "P14 requires left navigation to prioritize Phase -> Category and center workflow to render Subcategory -> Bucket -> Item, and unlocks readable canonical navigation and authority-safe documentation projection.", "P15. Panel must remain consumer-only.", "P15 requires Operator Panel to consume published runtime truth and never invent or patch semantic meaning ad hoc, and unlocks operational trust, reproducible progress and elimination of manual UI workaround logic.", "P16. Panel/DH bridge artifacts must exist.", "P16 observed support artifacts include hub_index.json, panel_manifest.json, panel_canonical_tree.json, panel_content_index.json, panel_navigation_spec.json, panel_component_contract.json, panel_data_contract.json, panel_sync_contract.json, panel_ui_blueprint.json and panel_runtime_bridge.json.", "P16 unlocks stable rendering, structural projection and future synchronization integrity." ] }, { "title": "Program maturity prerequisites still open", "items": [ "The project must explicitly preserve unresolved prerequisites as unresolved.", "Currently evidenced open prerequisites include reverse proxy, TLS baseline, Docker, Docker Compose, Nginx, full SSE bridge authority and full runtime publication maturity across all views.", "Open prerequisites may block downstream maturity, but they must never be hidden by UI completion cosmetics." ] }, { "title": "Exit rule", "items": [ "The prerequisites section is structurally complete only when it can answer, for every major project block: what exists.", "The prerequisites section is structurally complete only when it can answer, for every major project block: why it exists.", "The prerequisites section is structurally complete only when it can answer, for every major project block: where it enters the phase model.", "The prerequisites section is structurally complete only when it can answer, for every major project block: who governs it.", "The prerequisites section is structurally complete only when it can answer, for every major project block: what it depends on.", "The prerequisites section is structurally complete only when it can answer, for every major project block: what it unlocks next.", "The prerequisites section is structurally complete only when it can answer, for every major project block: which artifact is sovereign.", "The prerequisites section is structurally complete only when it can answer, for every major project block: which artifacts support it.", "The prerequisites section is structurally complete only when it can answer, for every major project block: how DH and Panel must project it downstream.", "If any of these questions cannot be answered materially, the prerequisite remains incomplete." ] } ] }, { "id": "installation", "label": "installation", "status": "ACTIVE", "buckets": [ { "title": "Installation scope", "items": [ "define that installation covers the full project path from server baseline to final Devon UI", "define that installation is phase-ordered, not random", "define that no downstream installation is valid without upstream dependency readiness" ] }, { "title": "Host and operating system baseline", "items": [ "provision server", "validate OS baseline", "validate kernel / architecture / disk / memory baseline", "create canonical paths", "create service users / permissions model", "define filesystem ownership" ] }, { "title": "Base tooling installation", "items": [ "Python3", "Git", "Curl", "package manager dependencies", "shell/runtime helpers", "archive / compression / transport utilities", "cron / timers if required" ] }, { "title": "Network, reverse proxy and transport baseline", "items": [ "DNS / hostname binding", "firewall policy", "SSH baseline", "reverse proxy installation", "Nginx installation", "TLS baseline", "certificate renewal path", "exposed port policy" ] }, { "title": "Container and service runtime", "items": [ "Docker installation", "Docker Compose installation", "image pull policy", "container network model", "persistent volume model", "restart policy", "service boot order" ] }, { "title": "Devon core path materialization", "items": [ "/opt/devon baseline", "canon directories", "bin directories", "runtime publication directories", "export/sync directories", "environment files", "permissions and executable bits" ] }, { "title": "Runtime contract base installation", "items": [ "runtime_expected_manifest.json", "runtime_probe_registry.json", "build_runtime_contracts.py", "runtime row semantics base", "project progress calculation base", "contract compilation flow" ] }, { "title": "Collector and publication pipeline", "items": [ "collect_runtime.py placement", "export bridge installation", "export_panel_runtime.sh", "publication target paths", "runtime artifact write permissions", "sync execution trigger", "failure-safe publication order" ] }, { "title": "Canon and governance layer installation", "items": [ "canon root materialization", "rules of operation", "decisions registry", "scope registry", "next action registry", "continuity file", "checkpoint strategy" ] }, { "title": "Architecture and authority document installation", "items": [ "master root registration", "scope authority", "deployment order authority", "phase 02 authority docs", "phase 03 contextual docs", "supporting JSON artifacts", "sovereign/support separation rule" ] }, { "title": "Security and trust installation", "items": [ "host security artifacts", "app security artifacts", "module security artifacts", "runtime security artifacts", "delivery security artifacts", "approval policy", "memory isolation controls", "security monitoring controls" ] }, { "title": "Memory, reasoning and tool execution installation", "items": [ "memory architecture", "memory lifecycle", "learning governance", "planning/reasoning controls", "tool execution controls", "knowledge ingestion", "trust-bound activation sequence" ] }, { "title": "Documentation Hub installation", "items": [ "hub_index.json", "source bindings", "structured category renderer", "navigation tree", "subcategory workflow rendering", "canon-source viewer integration" ] }, { "title": "Operator Panel / UI installation", "items": [ "panel manifest", "panel canonical tree", "panel navigation spec", "panel content index", "panel UI blueprint", "panel runtime bridge", "component contracts", "data contracts", "sync contracts" ] }, { "title": "Monitoring and real-time observability installation", "items": [ "monitoring canonical", "SSE bridge canonical", "host/container/service metrics path", "refresh/transport model", "alert and threshold base", "publication to UI path" ] }, { "title": "Installation dependency gates", "items": [ "host before runtime", "runtime contracts before collector", "collector before publication", "canon before DH/UI reflection", "trust before memory-bearing runtime", "monitoring before real-time operational completeness" ] }, { "title": "Open installation blockers", "items": [ "reverse proxy if still missing", "TLS if still missing", "Docker if still missing", "Docker Compose if still missing", "Nginx if still missing", "SSE if still planned only", "incomplete runtime publication maturity if still open" ] }, { "title": "Installation exit rule", "items": [ "installation is complete only when every required layer is materially present", "no phase is install-complete if downstream UI depends on artifacts that are still missing", "installation completion must be evidence-based, never inferred" ] } ] }, { "id": "configuration", "label": "configuration", "status": "ACTIVE", "buckets": [ { "title": "Configuration scope", "items": [ "define that configuration covers the full project path from server baseline to final Devon UI", "define that configuration is phase-ordered and dependency-bound", "define that no downstream configuration is valid without upstream installation readiness", "define that configuration completion must remain evidence-based and never inferred" ] }, { "title": "Host and operating system baseline configuration", "items": [ "hostname and server identity", "timezone, locale and clock baseline", "user, group and permission model", "filesystem ownership and path policy", "environment variable baseline", "service user boundaries", "resource baseline for CPU, memory and disk" ] }, { "title": "Base tooling and shell/runtime configuration", "items": [ "Python runtime path and execution policy", "Git baseline and repository access model", "Curl and transport utility baseline", "package manager sources and update policy", "shell helpers and runtime aliases if required", "archive / compression / transfer utility policy", "scheduler / cron / timer baseline if required" ] }, { "title": "Network, reverse proxy and transport configuration", "items": [ "DNS and hostname binding", "firewall rules and exposure policy", "SSH access baseline", "reverse proxy routing model", "Nginx vhost / upstream baseline", "TLS certificate and renewal baseline", "port exposure policy", "transport hardening and external access boundaries" ] }, { "title": "Container and service runtime configuration", "items": [ "Docker daemon baseline", "Docker Compose project model", "container network policy", "persistent volume policy", "image pull / version pinning policy", "restart policy", "service dependency order", "container environment file loading policy" ] }, { "title": "Devon core paths and environment configuration", "items": [ "/opt/devon path policy", "canon directory layout", "bin directory layout", "runtime publication directory policy", "export/sync directory policy", "environment file placement", "permissions and executable bits", "write/read ownership boundaries" ] }, { "title": "Runtime contracts and semantic model configuration", "items": [ "runtime_expected_manifest.json baseline", "runtime_probe_registry.json baseline", "build_runtime_contracts.py compilation path", "runtime row semantics configuration", "project progress model configuration", "stage completion semantic boundaries", "contract ownership and source-of-truth alignment" ] }, { "title": "Collector and publication pipeline configuration", "items": [ "collect_runtime.py execution model", "publication target path mapping", "export_panel_runtime.sh configuration", "artifact write permissions", "sync trigger policy", "failure-safe publication order", "consumer-side read-only expectations on Waresite" ] }, { "title": "Canon and governance layer configuration", "items": [ "canon root separation from panel/data", "rules of operation in force", "decision registry policy", "scope registry policy", "next action continuity policy", "checkpoint strategy", "context reconstruction rule" ] }, { "title": "Architecture and authority document configuration", "items": [ "master root registration policy", "scope authority boundaries", "deployment order authority boundaries", "phase 02 authority ownership", "phase 03 contextual ownership", "supporting JSON artifact alignment", "sovereign/support separation rule" ] }, { "title": "Security and trust configuration", "items": [ "host security baseline", "application security baseline", "module security baseline", "runtime security baseline", "delivery security baseline", "approval policy", "memory isolation boundaries", "security monitoring boundaries" ] }, { "title": "Memory, reasoning and tool execution configuration", "items": [ "memory architecture baseline", "memory lifecycle policy", "learning governance boundaries", "planning/reasoning control model", "tool execution permission model", "knowledge ingestion boundaries", "trust-bound activation order" ] }, { "title": "Documentation Hub configuration", "items": [ "hub_index.json structure", "source binding rules", "structured category renderer behavior", "navigation tree policy", "subcategory workflow rendering", "canon-source viewer integration", "DH projection must remain subordinate to canon" ] }, { "title": "Operator Panel / UI configuration", "items": [ "panel manifest configuration", "panel canonical tree configuration", "panel navigation spec configuration", "panel content index configuration", "panel UI blueprint configuration", "panel runtime bridge configuration", "component contract alignment", "data contract alignment", "sync contract alignment" ] }, { "title": "Monitoring and real-time observability configuration", "items": [ "monitoring canonical baseline", "SSE bridge configuration baseline", "host/container/service metric routing", "refresh / transport cadence", "alert and threshold baseline", "runtime-to-UI publication path", "real-time observability trust boundaries" ] }, { "title": "Configuration dependency gates", "items": [ "host before runtime", "runtime contracts before collector", "collector before publication", "canon before DH/UI reflection", "trust before memory-bearing runtime", "monitoring before real-time operational completeness" ] }, { "title": "Open configuration blockers", "items": [ "reverse proxy if still missing", "TLS if still missing", "Docker if still missing", "Docker Compose if still missing", "Nginx if still missing", "SSE if still planned only", "incomplete runtime publication maturity if still open" ] }, { "title": "Configuration exit rule", "items": [ "configuration is complete only when every required layer is materially aligned", "no phase is config-complete if downstream UI depends on artifacts that remain missing or misconfigured", "configuration completion must be evidence-based, never inferred" ] } ] }, { "id": "validation", "label": "validation", "status": "ACTIVE", "buckets": [ { "title": "Validation scope", "items": [ "define that validation covers the full project path from server baseline to final Devon UI", "define that validation must be phase-ordered and dependency-aware", "define that no downstream layer may be treated as valid without upstream validation readiness", "define that validation completion must be evidence-based, never inferred" ] }, { "title": "Validation model and status law", "items": [ "validation resolves only through PASS, FAIL, MISSING or PLANNED", "PASS means observable evidence exists and validation succeeds", "FAIL means observable evidence exists and validation fails", "MISSING means required evidence does not exist materially", "PLANNED means the layer is formally defined but not materially present" ] }, { "title": "Host and operating system validation", "items": [ "validate server existence and host identity", "validate OS baseline", "validate kernel and architecture compatibility", "validate disk and memory baseline", "validate service exposure baseline", "validate user, group and permission baseline" ] }, { "title": "Filesystem and path validation", "items": [ "validate canonical root paths", "validate /opt/devon baseline", "validate /home/yeff/public_html/devon baseline", "validate canon directory layout", "validate bin directory layout", "validate runtime publication directories", "validate export/sync directories", "validate environment files and permission bits" ] }, { "title": "Base tooling validation", "items": [ "validate Python3 availability and execution path", "validate Git availability and repository access", "validate Curl availability", "validate package/runtime helpers if required", "validate archive / compression / transport utilities if required", "validate cron / timers if required" ] }, { "title": "Network, proxy and transport validation", "items": [ "validate DNS / hostname binding", "validate firewall policy", "validate SSH baseline", "validate reverse proxy presence and routing", "validate Nginx presence and configuration", "validate TLS presence and renewal path", "validate exposed port policy", "validate transport hardening boundaries" ] }, { "title": "Container and service runtime validation", "items": [ "validate Docker presence and daemon state", "validate Docker Compose presence", "validate container network model", "validate persistent volume model", "validate image pull / version pinning policy", "validate restart policy behavior", "validate service dependency order", "validate container environment loading" ] }, { "title": "Runtime contract and semantic validation", "items": [ "validate runtime_expected_manifest.json", "validate runtime_probe_registry.json", "validate build_runtime_contracts.py execution path", "validate runtime row semantics alignment", "validate project progress model alignment", "validate stage completion semantic boundaries", "validate source-of-truth ownership" ] }, { "title": "Collector and publication pipeline validation", "items": [ "validate collect_runtime.py execution", "validate collector output completeness", "validate export_panel_runtime.sh execution", "validate publication target paths", "validate runtime artifact write permissions", "validate sync trigger behavior", "validate failure-safe publication order", "validate Waresite consumer-side artifact refresh" ] }, { "title": "Runtime artifact validation", "items": [ "validate runtime_snapshot.json", "validate runtime_status.json", "validate host_runtime.json", "validate docker_runtime.json", "validate project_progress.json", "validate artifact refresh behavior", "validate artifact content against declared semantic contract" ] }, { "title": "Canon and governance validation", "items": [ "validate canon root existence and separation from panel/data", "validate rules of operation in force", "validate decisions registry", "validate scope registry", "validate next action registry", "validate continuity file", "validate checkpoint strategy", "validate context reconstruction rule compliance" ] }, { "title": "Architecture and authority validation", "items": [ "validate master root registration", "validate scope authority boundaries", "validate deployment order authority boundaries", "validate phase 02 authority docs", "validate phase 03 contextual docs", "validate supporting JSON artifacts", "validate sovereign/support separation" ] }, { "title": "Security and trust validation", "items": [ "validate host security baseline", "validate application security baseline", "validate module security baseline", "validate runtime security baseline", "validate delivery security baseline", "validate approval policy", "validate memory isolation boundaries", "validate security monitoring boundaries" ] }, { "title": "Memory, reasoning and tool execution validation", "items": [ "validate memory architecture baseline", "validate memory lifecycle policy", "validate learning governance boundaries", "validate planning/reasoning control model", "validate tool execution permission model", "validate knowledge ingestion boundaries", "validate trust-bound activation order" ] }, { "title": "Documentation Hub and Panel validation", "items": [ "validate hub_index.json readability and structure", "validate source binding rules", "validate structured category renderer behavior", "validate navigation tree integrity", "validate subcategory workflow rendering", "validate canon-source viewer integration", "validate panel manifest, tree, content index and blueprint alignment", "validate that UI reads published truth rather than inventing local state" ] }, { "title": "Monitoring and real-time observability validation", "items": [ "validate monitoring canonical baseline", "validate SSE bridge baseline or explicit planned status", "validate host/container/service metric routing", "validate refresh / transport cadence", "validate alert and threshold baseline", "validate runtime-to-UI publication path", "validate real-time observability trust boundaries" ] }, { "title": "Validation dependency gates", "items": [ "validate host before runtime", "validate runtime contracts before collector", "validate collector before publication", "validate canon before DH/UI reflection", "validate trust before memory-bearing runtime", "validate monitoring before real-time operational completeness" ] }, { "title": "Open validation blockers", "items": [ "reverse proxy if still missing", "TLS if still missing", "Docker if still missing", "Docker Compose if still missing", "Nginx if still missing", "SSE if still planned only", "incomplete runtime publication maturity if still open", "any downstream UI claim not backed by deterministic evidence" ] }, { "title": "Validation exit rule", "items": [ "validation is complete only when every required layer has deterministic proof of correctness", "no phase is validation-complete if downstream UI depends on missing, broken or non-validated artifacts", "validation completion must be evidence-based, never inferred" ] } ] }, { "id": "observable_evidence", "label": "observable_evidence", "status": "ACTIVE", "buckets": [ { "title": "Evidence scope", "items": [ "define that observable evidence covers the full project path from server baseline to final Devon UI", "define that only materially observable state counts as valid evidence", "define that no downstream phase may claim readiness without upstream observable evidence", "define that evidence must be server-bound, artifact-bound or runtime-bound, never inferred" ] }, { "title": "Host and operating system evidence", "items": [ "server exists materially", "hostname is observable", "operating system baseline is observable", "kernel and architecture are observable", "disk and memory baseline are observable", "exposed listening services are observable", "user, group and permission baseline are observable" ] }, { "title": "Filesystem and path evidence", "items": [ "canonical root paths exist materially", "/opt/devon baseline is observable", "/home/yeff/public_html/devon baseline is observable", "canon directories are observable", "bin directories are observable", "runtime publication directories are observable", "export/sync directories are observable", "environment files and permission bits are observable" ] }, { "title": "Base tooling evidence", "items": [ "Python3 is observable", "Git is observable", "Curl is observable", "package/runtime helpers are observable if required", "archive / compression / transport utilities are observable if required", "cron / timers are observable if required" ] }, { "title": "Network, proxy and transport evidence", "items": [ "DNS / hostname binding is observable", "firewall policy is observable", "SSH baseline is observable", "reverse proxy presence is observable", "Nginx presence is observable", "TLS material presence is observable", "certificate renewal path is observable", "exposed port policy is observable" ] }, { "title": "Container and service runtime evidence", "items": [ "Docker presence is observable", "Docker Compose presence is observable", "container runtime state is observable", "image pull state is observable", "container network state is observable", "persistent volumes are observable", "restart policy behavior is observable", "service boot order effects are observable" ] }, { "title": "Devon core path and environment evidence", "items": [ "/opt/devon structure exists materially", "canon files exist materially", "executable scripts exist materially", "runtime publication paths exist materially", "export/sync paths exist materially", "environment file placement is observable", "permissions and executable bits are observable", "ownership boundaries are observable" ] }, { "title": "Runtime contract evidence", "items": [ "runtime_expected_manifest.json exists", "runtime_probe_registry.json exists", "build_runtime_contracts.py exists", "runtime row semantics base exists", "project progress calculation base exists", "contract compilation output is observable", "semantic field preservation is observable in published artifacts" ] }, { "title": "Collector and publication pipeline evidence", "items": [ "collect_runtime.py exists materially", "collector output is observable", "export_panel_runtime.sh exists materially", "publication target paths are observable", "runtime artifact writes are observable", "sync execution is observable", "failure-safe publication order is observable", "Waresite consumer-side artifacts are observable after export" ] }, { "title": "Runtime artifact evidence", "items": [ "runtime_snapshot.json exists", "runtime_status.json exists", "host_runtime.json exists", "docker_runtime.json exists", "project_progress.json exists", "artifact timestamps and refresh behavior are observable", "artifact content matches declared semantic contract" ] }, { "title": "Canon and governance evidence", "items": [ "canon root exists materially", "rules of operation file exists", "decisions registry exists", "scope registry exists", "next action registry exists", "continuity file exists", "checkpoint materialization is observable", "root separation between canon and panel/data is observable" ] }, { "title": "Architecture and authority evidence", "items": [ "master root registration is observable", "scope authority is observable", "deployment order authority is observable", "phase 02 authority docs are observable", "phase 03 contextual docs are observable", "supporting JSON artifacts are observable", "sovereign/support separation is observable in file placement and usage" ] }, { "title": "Security and trust evidence", "items": [ "host security artifacts exist", "app security artifacts exist", "module security artifacts exist", "runtime security artifacts exist", "delivery security artifacts exist", "approval policy artifact exists", "memory isolation controls are observable", "security monitoring controls are observable" ] }, { "title": "Memory, reasoning and tool execution evidence", "items": [ "memory architecture artifact exists", "memory lifecycle artifact exists", "learning governance artifact exists", "planning/reasoning artifact exists", "tool execution artifact exists", "knowledge ingestion artifact exists", "trust-bound activation sequence is observable in canon and downstream projection" ] }, { "title": "Documentation Hub evidence", "items": [ "hub_index.json exists and is readable", "source bindings are observable", "structured category renderer behavior is observable", "navigation tree is observable", "subcategory workflow rendering is observable", "canon-source viewer integration is observable", "DH projection remains subordinate to canon" ] }, { "title": "Operator Panel / UI evidence", "items": [ "panel manifest exists", "panel canonical tree exists", "panel navigation spec exists", "panel content index exists", "panel UI blueprint exists", "panel runtime bridge exists", "component contracts exist", "data contracts exist", "sync contracts exist", "UI reads published truth rather than inventing state locally" ] }, { "title": "Monitoring and real-time observability evidence", "items": [ "monitoring canonical exists", "SSE bridge canonical exists or remains explicitly planned", "host/container/service metric path is observable", "refresh/transport behavior is observable", "alert and threshold baseline is observable", "publication to UI path is observable", "real-time observability boundaries are observable" ] }, { "title": "Evidence dependency gates", "items": [ "host evidence before runtime evidence", "runtime contract evidence before collector evidence", "collector evidence before publication evidence", "canon evidence before DH/UI reflection evidence", "trust evidence before memory-bearing runtime evidence", "monitoring evidence before real-time operational completeness evidence" ] }, { "title": "Open evidence gaps", "items": [ "reverse proxy if still missing", "TLS if still missing", "Docker if still missing", "Docker Compose if still missing", "Nginx if still missing", "SSE if still planned only", "incomplete runtime publication maturity if still open", "any downstream UI claim not backed by server or artifact evidence" ] }, { "title": "Observable evidence exit rule", "items": [ "observable evidence is complete only when every required layer has material proof", "no phase is evidence-complete if downstream UI depends on missing or non-observable artifacts", "evidence completion must be based on observable server state, published artifacts or deterministic UI projection of those artifacts", "anything not materially observable remains MISSING" ] } ] }, { "id": "failure_modes_recovery", "label": "failure_modes_recovery", "status": "ACTIVE", "buckets": [ { "title": "Failure modes scope", "items": [ "define that failure modes and recovery cover the full project path from server baseline to final Devon UI", "define that failure modes must be treated as operational realities, not edge-case afterthoughts", "define that recovery paths must be deterministic, evidence-based and phase-aware", "define that no downstream layer may hide upstream failure conditions" ] }, { "title": "Host and operating system failures", "items": [ "server unavailable or partially degraded", "OS baseline drift", "kernel or architecture mismatch", "disk exhaustion", "memory pressure or swap exhaustion", "permission or ownership corruption", "service user or execution boundary failure" ] }, { "title": "Filesystem and path failures", "items": [ "missing canonical root paths", "missing /opt/devon baseline", "broken canon directory layout", "missing runtime publication directories", "broken export/sync paths", "missing environment files", "incorrect executable bits", "write path denied by ownership or permissions" ] }, { "title": "Base tooling failures", "items": [ "Python runtime unavailable or mismatched", "Git unavailable or repository access broken", "Curl unavailable or transport helpers missing", "package/runtime helper mismatch", "archive / compression / transfer utilities unavailable", "scheduler / cron / timer path missing if required" ] }, { "title": "Network, proxy and transport failures", "items": [ "DNS or hostname mismatch", "firewall policy blocks expected exposure", "SSH baseline unavailable", "reverse proxy missing or misrouted", "Nginx missing or misconfigured", "TLS missing, expired or broken", "certificate renewal path broken", "port exposure diverges from policy" ] }, { "title": "Container and service runtime failures", "items": [ "Docker unavailable or daemon not running", "Docker Compose unavailable", "container network broken", "persistent volume path missing or detached", "restart policy not honored", "service boot order broken", "image pull or version pinning failure", "container environment loading failure" ] }, { "title": "Runtime contract and semantic failures", "items": [ "runtime_expected_manifest.json missing or stale", "runtime_probe_registry.json missing or stale", "build_runtime_contracts.py missing or failing", "runtime row semantics missing or inconsistent", "project progress model drift", "stage completion semantics corrupted", "source-of-truth boundary violated" ] }, { "title": "Collector and publication pipeline failures", "items": [ "collect_runtime.py missing or failing", "collector output incomplete or stale", "export_panel_runtime.sh missing or failing", "publication target path broken", "runtime artifact writes denied", "sync trigger missing or unreliable", "publication order not failure-safe", "Waresite consumer artifacts stale after export" ] }, { "title": "Runtime artifact failures", "items": [ "runtime_snapshot.json missing or stale", "runtime_status.json missing or stale", "host_runtime.json missing or stale", "docker_runtime.json missing or stale", "project_progress.json missing or stale", "artifact timestamps no longer refresh", "artifact content no longer matches semantic contract" ] }, { "title": "Canon and governance failures", "items": [ "canon root missing or mixed with panel/data", "rules of operation drift or absence", "decisions registry drift or absence", "scope registry drift or absence", "next action registry missing", "continuity file missing or stale", "checkpoint strategy broken", "context reconstruction rule bypassed" ] }, { "title": "Architecture and authority failures", "items": [ "master root registration broken", "scope authority drift", "deployment order authority drift", "phase 02 authority docs missing or stale", "phase 03 contextual docs missing or stale", "supporting JSON artifacts missing or stale", "sovereign/support separation violated" ] }, { "title": "Security and trust failures", "items": [ "host security artifacts missing", "app security artifacts missing", "module security artifacts missing", "runtime security artifacts missing", "delivery security artifacts missing", "approval policy missing or bypassed", "memory isolation broken", "security monitoring absent or stale" ] }, { "title": "Memory, reasoning and tool execution failures", "items": [ "memory architecture artifact missing", "memory lifecycle artifact missing", "learning governance artifact missing", "planning/reasoning artifact missing", "tool execution artifact missing", "knowledge ingestion artifact missing", "trust-bound activation order violated" ] }, { "title": "Documentation Hub and UI failures", "items": [ "hub_index.json unreadable or structurally broken", "source bindings broken", "structured category renderer drift", "navigation tree broken", "subcategory workflow rendering broken", "canon-source viewer integration broken", "UI projects stale or invented state instead of published truth" ] }, { "title": "Monitoring and real-time observability failures", "items": [ "monitoring canonical missing or stale", "SSE bridge canonical missing or only planned", "host/container/service metric path broken", "refresh / transport cadence broken", "alert and threshold baseline absent", "publication to UI path broken", "real-time observability trust boundaries violated" ] }, { "title": "Recovery model", "items": [ "restore source-of-truth boundaries first", "restore upstream dependency before downstream projection", "restore paths and permissions before runtime execution", "restore contracts before collector", "restore collector before publication", "restore publication before DH/UI trust" ] }, { "title": "Recovery dependency gates", "items": [ "host recovery before runtime recovery", "runtime contract recovery before collector recovery", "collector recovery before publication recovery", "canon recovery before DH/UI recovery", "trust recovery before memory-bearing runtime recovery", "monitoring recovery before real-time operational completeness recovery" ] }, { "title": "Failure visibility rule", "items": [ "any missing observable layer remains MISSING", "any broken but observable layer remains FAIL", "no UI completion may conceal unresolved failure state", "no recovery may be declared complete without material evidence" ] }, { "title": "Failure modes and recovery exit rule", "items": [ "failure handling is complete only when every required broken layer has a deterministic recovery path", "recovery is complete only when upstream dependencies are restored before downstream consumers rely on them", "recovery completion must be evidence-based, never inferred" ] } ] }, { "id": "completion_promotion", "label": "completion_promotion", "status": "ACTIVE", "buckets": [ { "title": "Completion and promotion scope", "items": [ "define that completion and promotion cover the full project path from server baseline to final Devon UI", "define that completion is phase-ordered and dependency-bound", "define that promotion is only valid after upstream completion is materially proven", "define that no downstream layer may be promoted if upstream completion remains missing, failed or unvalidated" ] }, { "title": "Completion model and promotion law", "items": [ "completion must be determined by observable evidence, not by declared intent", "promotion must follow dependency order rather than cosmetic UI readiness", "no phase is complete if downstream consumers still depend on missing or broken upstream artifacts", "promotion must remain blocked when source-of-truth boundaries are unresolved", "completion and promotion must resolve through PASS, FAIL, MISSING or PLANNED" ] }, { "title": "Host and operating system completion", "items": [ "server baseline exists materially", "OS baseline is stable and validated", "kernel, architecture, disk and memory baseline are validated", "service exposure baseline is validated", "user, group and permission model is stable", "host is ready to unblock downstream runtime and publication layers" ] }, { "title": "Filesystem and path completion", "items": [ "canonical root paths exist materially", "/opt/devon baseline is complete", "/home/yeff/public_html/devon baseline is complete", "canon directory layout is complete", "bin directory layout is complete", "runtime publication directories are complete", "export/sync directories are complete", "environment files, permissions and executable bits are complete" ] }, { "title": "Base tooling completion", "items": [ "Python3 is installed, observable and validated", "Git is installed, observable and validated", "Curl is installed, observable and validated", "package/runtime helpers are complete if required", "archive / compression / transport utilities are complete if required", "cron / timers are complete if required" ] }, { "title": "Network, proxy and transport completion", "items": [ "DNS / hostname binding is complete", "firewall policy is complete", "SSH baseline is complete", "reverse proxy is complete if required", "Nginx is complete if required", "TLS baseline is complete if required", "certificate renewal path is complete if required", "port exposure policy is complete" ] }, { "title": "Container and service runtime completion", "items": [ "Docker is complete if required", "Docker Compose is complete if required", "container network model is complete", "persistent volume model is complete", "image pull / version pinning policy is complete", "restart policy behavior is complete", "service dependency order is complete", "container environment loading is complete" ] }, { "title": "Runtime contract and semantic completion", "items": [ "runtime_expected_manifest.json is complete and current", "runtime_probe_registry.json is complete and current", "build_runtime_contracts.py path and execution are complete", "runtime row semantics are complete and stable", "project progress model is complete and aligned", "stage completion semantic boundaries are complete", "source-of-truth ownership is complete and stable" ] }, { "title": "Collector and publication pipeline completion", "items": [ "collect_runtime.py is complete and validated", "collector output is complete", "export_panel_runtime.sh is complete and validated", "publication target paths are complete", "runtime artifact write permissions are complete", "sync trigger behavior is complete", "failure-safe publication order is complete", "Waresite consumer-side artifact refresh is complete" ] }, { "title": "Runtime artifact completion", "items": [ "runtime_snapshot.json is complete and current", "runtime_status.json is complete and current", "host_runtime.json is complete and current", "docker_runtime.json is complete and current", "project_progress.json is complete and current", "artifact refresh behavior is complete", "artifact content remains aligned with the semantic contract" ] }, { "title": "Canon and governance completion", "items": [ "canon root is complete and separated from panel/data", "rules of operation are complete and in force", "decisions registry is complete", "scope registry is complete", "next action registry is complete", "continuity file is complete", "checkpoint strategy is complete", "context reconstruction rule remains enforced" ] }, { "title": "Architecture and authority completion", "items": [ "master root registration is complete", "scope authority boundaries are complete", "deployment order authority boundaries are complete", "phase 02 authority docs are complete", "phase 03 contextual docs are complete", "supporting JSON artifacts are complete", "sovereign/support separation is complete" ] }, { "title": "Security and trust completion", "items": [ "host security baseline is complete", "application security baseline is complete", "module security baseline is complete", "runtime security baseline is complete", "delivery security baseline is complete", "approval policy is complete", "memory isolation boundaries are complete", "security monitoring boundaries are complete" ] }, { "title": "Memory, reasoning and tool execution completion", "items": [ "memory architecture baseline is complete", "memory lifecycle policy is complete", "learning governance boundaries are complete", "planning/reasoning control model is complete", "tool execution permission model is complete", "knowledge ingestion boundaries are complete", "trust-bound activation order is complete" ] }, { "title": "Documentation Hub and Panel completion", "items": [ "hub_index.json structure is complete and readable", "source binding rules are complete", "structured category renderer behavior is complete", "navigation tree integrity is complete", "subcategory workflow rendering is complete", "canon-source viewer integration is complete", "panel manifest, tree, content index and blueprint are complete", "UI reads published truth rather than inventing local state" ] }, { "title": "Monitoring and real-time observability completion", "items": [ "monitoring canonical baseline is complete", "SSE bridge baseline is complete or remains explicitly planned", "host/container/service metric routing is complete", "refresh / transport cadence is complete", "alert and threshold baseline is complete", "runtime-to-UI publication path is complete", "real-time observability trust boundaries are complete" ] }, { "title": "Promotion dependency gates", "items": [ "host completion before runtime promotion", "runtime contract completion before collector promotion", "collector completion before publication promotion", "canon completion before DH/UI reflection promotion", "trust completion before memory-bearing runtime promotion", "monitoring completion before real-time operational completeness promotion" ] }, { "title": "Promotion blockers", "items": [ "reverse proxy if still missing", "TLS if still missing", "Docker if still missing", "Docker Compose if still missing", "Nginx if still missing", "SSE if still planned only", "incomplete runtime publication maturity if still open", "any downstream UI claim not backed by completed and validated upstream layers" ] }, { "title": "Completion and promotion exit rule", "items": [ "completion is valid only when every required layer has material proof of readiness", "promotion is valid only when upstream dependencies are complete, validated and stable", "no phase is promotion-complete if downstream UI depends on missing, broken or unstable artifacts", "completion and promotion must remain evidence-based, never inferred" ] } ] } ] }, { "id": "architecture_engineering_core", "title": "Architecture & Engineering Canon", "sub": "authority and satellite documents for architecture, governance, contracts, naming, deployment and contextual boundaries.", "badge": "phase 02", "docs": [ { "id": "cas", "title": "CAS · Cognitive Architecture Spec", "path": "../panel/data/cas.md", "phase": "phase-02", "layer": "architecture_engineering_core", "role": "Primary authority for cognitive architecture placement.", "fits": "Owns architecture layers and separation between probabilistic and deterministic components.", "depends_on": [ "master_architecture_index" ], "used_by": [ "cfc", "ccc", "lpc", "sec", "ofc" ], "architecture_view": "Sovereign architecture meaning.", "label": "CAS · Cognitive Architecture Spec", "type": "text" }, { "id": "cgs", "title": "CGS · Canonical Governance Spec", "path": "../panel/data/cgs.md", "phase": "phase-02", "layer": "architecture_engineering_core", "role": "Primary governance authority.", "fits": "Owns governance structure and canonical responsibility boundaries.", "depends_on": [ "master_architecture_index" ], "used_by": [], "architecture_view": "Governance backbone of the structural canon.", "label": "CGS · Canonical Governance Spec", "type": "text" }, { "id": "acs", "title": "ACS · Artifact Canon Structure", "path": "../panel/data/acs.md", "phase": "phase-02", "layer": "architecture_engineering_core", "role": "Primary artifact canon authority.", "fits": "Defines artifact structure and canonical placement logic.", "depends_on": [ "master_architecture_index" ], "used_by": [], "architecture_view": "Artifact structure ownership.", "label": "ACS · Artifact Canon Structure", "type": "text" }, { "id": "css", "title": "CSS · Contracts & Schemas Spec", "path": "../panel/data/css.md", "phase": "phase-02", "layer": "architecture_engineering_core", "role": "Primary contracts and schemas authority.", "fits": "Owns contracts, schema legitimacy and structured interfaces.", "depends_on": [ "master_architecture_index" ], "used_by": [], "architecture_view": "Schema and contract sovereignty.", "label": "CSS · Contracts & Schemas Spec", "type": "text" }, { "id": "ncs", "title": "NCS · Naming Canon Spec", "path": "../panel/data/ncs.md", "phase": "phase-02", "layer": "architecture_engineering_core", "role": "Primary naming authority.", "fits": "Owns naming legitimacy across canon artifacts.", "depends_on": [ "master_architecture_index" ], "used_by": [], "architecture_view": "Naming governance surface.", "label": "NCS · Naming Canon Spec", "type": "text" }, { "id": "sts", "title": "STS · State Transition Spec", "path": "../panel/data/sts.md", "phase": "phase-02", "layer": "architecture_engineering_core", "role": "Primary state legitimacy authority.", "fits": "Owns state legitimacy and transition boundary rules.", "depends_on": [ "master_architecture_index" ], "used_by": [ "cfc", "ofc" ], "architecture_view": "State governance authority.", "label": "STS · State Transition Spec", "type": "text" }, { "id": "brps", "title": "BRPS · Build Release Promotion Spec", "path": "../panel/data/brps.md", "phase": "phase-02", "layer": "architecture_engineering_core", "role": "Primary release and promotion authority.", "fits": "Owns build, release and promotion rules, including packaging audit, SBOM, sourcemap blocking, sensitive artifact protection and environment-aware promotion safeguards.", "depends_on": [ "master_architecture_index" ], "used_by": [], "architecture_view": "Promotion governance surface with release packaging safeguards.", "label": "BRPS · Build Release Promotion Spec", "type": "text" }, { "id": "cdms", "title": "CDMS · Canonical Deployment Model Spec", "path": "../panel/data/cdms.md", "phase": "phase-02", "layer": "architecture_engineering_core", "role": "Primary deployment structure authority.", "fits": "Owns deployment structure and placement boundaries.", "depends_on": [ "master_architecture_index" ], "used_by": [], "architecture_view": "Deployment structure authority.", "label": "CDMS · Canonical Deployment Model Spec", "type": "text" }, { "id": "ris", "title": "RIS · Role Interaction Spec", "path": "../panel/data/ris.md", "phase": "phase-02", "layer": "architecture_engineering_core", "role": "Satellite contextual document.", "fits": "Provides role interaction context without redefining sovereign authority.", "depends_on": [ "cas", "cfc" ], "used_by": [], "architecture_view": "Contextual relation layer.", "label": "RIS · Role Interaction Spec", "type": "text" }, { "id": "ofms", "title": "OFMS · Operational Flow Mapping Spec", "path": "../panel/data/ofms.md", "phase": "phase-02", "layer": "architecture_engineering_core", "role": "Satellite contextual document.", "fits": "Provides contextual flow mapping without redefining canonical flow.", "depends_on": [ "cfc", "ofc" ], "used_by": [], "architecture_view": "Contextual flow map.", "label": "OFMS · Operational Flow Mapping Spec", "type": "text" }, { "id": "card_contract_minimums", "title": "Card Contract Minimums", "path": "../panel/data/card_contract_minimums.json", "phase": "phase-02", "layer": "architecture_engineering_core", "role": "Structured contract support artifact.", "fits": "Defines minimum card contract fields for panel and documentation surfaces.", "depends_on": [ "css" ], "used_by": [], "architecture_view": "Contract minimum support layer.", "label": "Card Contract Minimums", "type": "json" }, { "id": "panel_data_contract", "title": "Panel Data Contract", "path": "../panel/data/panel_data_contract.json", "phase": "phase-02", "layer": "architecture_engineering_core", "role": "Structured panel data contract authority.", "fits": "Defines machine-readable panel data contract boundaries.", "depends_on": [ "css" ], "used_by": [], "architecture_view": "Panel data contract support layer.", "label": "Panel Data Contract", "type": "json" }, { "id": "panel_component_contract", "title": "Panel Component Contract", "path": "../panel/data/panel_component_contract.json", "phase": "phase-02", "layer": "architecture_engineering_core", "role": "Structured panel component contract authority.", "fits": "Defines machine-readable component contract boundaries.", "depends_on": [ "css" ], "used_by": [], "architecture_view": "Panel component contract support layer.", "label": "Panel Component Contract", "type": "json" }, { "id": "panel_sync_contract", "title": "Panel Sync Contract", "path": "../panel/data/panel_sync_contract.json", "phase": "phase-02", "layer": "architecture_engineering_core", "role": "Structured panel sync contract authority.", "fits": "Defines machine-readable sync contract boundaries.", "depends_on": [ "css" ], "used_by": [], "architecture_view": "Panel sync contract support layer.", "label": "Panel Sync Contract", "type": "json" }, { "id": "panel_canonical_tree", "title": "Panel Canonical Tree", "path": "../panel/data/panel_canonical_tree.json", "phase": "phase-02", "layer": "architecture_engineering_core", "role": "Primary panel canonical tree authority.", "fits": "Defines structural panel tree and canonical UI grouping.", "depends_on": [ "master_architecture_index" ], "used_by": [], "architecture_view": "Panel tree authority.", "label": "Panel Canonical Tree", "type": "json" }, { "id": "panel_navigation_spec", "title": "Panel Navigation Spec", "path": "../panel/data/panel_navigation_spec.json", "phase": "phase-02", "layer": "architecture_engineering_core", "role": "Primary panel navigation authority.", "fits": "Defines canonical panel navigation structure.", "depends_on": [ "master_architecture_index" ], "used_by": [], "architecture_view": "Panel navigation authority.", "label": "Panel Navigation Spec", "type": "json" }, { "id": "panel_ui_blueprint", "title": "Panel UI Blueprint", "path": "../panel/data/panel_ui_blueprint.json", "phase": "phase-02", "layer": "architecture_engineering_core", "role": "Primary panel UI blueprint authority.", "fits": "Defines canonical panel UI blueprint expectations.", "depends_on": [ "master_architecture_index" ], "used_by": [], "architecture_view": "Panel UI blueprint authority.", "label": "Panel UI Blueprint", "type": "json" }, { "id": "canonical_matrix_v1", "title": "Canonical Matrix v1", "path": "../panel/data/canonical_matrix_v1.json", "phase": "phase-02", "layer": "architecture_engineering_core", "role": "Primary canonical matrix authority.", "fits": "Defines machine-readable canonical matrix structure.", "depends_on": [ "master_architecture_index" ], "used_by": [], "architecture_view": "Canonical matrix authority.", "label": "Canonical Matrix v1", "type": "json" } ], "phase_id": "phase-02", "subcategories": [ { "id": "prerequisites", "label": "prerequisites", "status": "MISSING", "buckets": [] }, { "id": "installation", "label": "installation", "status": "MISSING", "buckets": [] }, { "id": "configuration", "label": "configuration", "status": "MISSING", "buckets": [] }, { "id": "validation", "label": "validation", "status": "MISSING", "buckets": [] }, { "id": "observable_evidence", "label": "observable_evidence", "status": "MISSING", "buckets": [] }, { "id": "failure_modes_recovery", "label": "failure_modes_recovery", "status": "MISSING", "buckets": [] }, { "id": "completion_promotion", "label": "completion_promotion", "status": "MISSING", "buckets": [] } ] }, { "id": "cognitive_flow", "title": "Cognitive Flow Canon", "sub": "deterministic orchestration, validation order, execution gating and flow control.", "badge": "phase 03", "docs": [ { "id": "cfc", "title": "CFC · Cognitive Flow Canon", "path": "../panel/data/cfc.md", "phase": "phase-03", "layer": "cognitive_flow", "role": "Primary authority for deterministic orchestration.", "fits": "Owns governed flow, validation order and execution permission.", "depends_on": [ "cas", "sts" ], "used_by": [ "ofc", "lpc", "ris" ], "architecture_view": "Sovereign flow meaning.", "label": "CFC · Cognitive Flow Canon", "type": "text" }, { "id": "ccc", "title": "CCC · Cognitive Component Context", "path": "../panel/data/ccc.md", "phase": "phase-03", "layer": "cognitive_flow", "role": "Contextual component reference.", "fits": "Describes cognitive component relationships without redefining sovereign flow authority.", "depends_on": [ "cfc", "cas" ], "used_by": [], "architecture_view": "Contextual support layer for Phase 03 cognitive flow.", "label": "CCC · Cognitive Component Context", "type": "text" } ], "phase_id": "phase-03", "subcategories": [ { "id": "prerequisites", "label": "prerequisites", "status": "MISSING", "buckets": [] }, { "id": "installation", "label": "installation", "status": "MISSING", "buckets": [] }, { "id": "configuration", "label": "configuration", "status": "MISSING", "buckets": [] }, { "id": "validation", "label": "validation", "status": "MISSING", "buckets": [] }, { "id": "observable_evidence", "label": "observable_evidence", "status": "MISSING", "buckets": [] }, { "id": "failure_modes_recovery", "label": "failure_modes_recovery", "status": "MISSING", "buckets": [] }, { "id": "completion_promotion", "label": "completion_promotion", "status": "MISSING", "buckets": [] } ] }, { "id": "containerization", "title": "Containerization Canon", "sub": "deployment topology, service isolation and runtime/container boundaries under sovereign Phase 04 authority.", "badge": "phase 04", "docs": [ { "id": "cdms", "title": "CDMS · Canonical Deployment Model Spec", "path": "../panel/data/cdms.md", "phase": "phase-04", "layer": "containerization", "role": "Primary deployment structure and containerization authority.", "fits": "Owns container topology, isolation boundaries and deployment placement for Phase 04.", "depends_on": [ "cas", "cfc", "server_registry" ], "used_by": [], "architecture_view": "Sovereign Phase 04 containerization authority.", "label": "CDMS · Canonical Deployment Model Spec", "type": "text" } ], "phase_id": "phase-04", "subcategories": [ { "id": "prerequisites", "label": "prerequisites", "status": "MISSING", "buckets": [] }, { "id": "installation", "label": "installation", "status": "MISSING", "buckets": [] }, { "id": "configuration", "label": "configuration", "status": "MISSING", "buckets": [] }, { "id": "validation", "label": "validation", "status": "MISSING", "buckets": [] }, { "id": "observable_evidence", "label": "observable_evidence", "status": "MISSING", "buckets": [] }, { "id": "failure_modes_recovery", "label": "failure_modes_recovery", "status": "MISSING", "buckets": [] }, { "id": "completion_promotion", "label": "completion_promotion", "status": "MISSING", "buckets": [] } ] }, { "id": "latency_performance", "title": "Latency & Performance Canon", "sub": "latency model, hot path, cold path and bounded performance design.", "badge": "phase 05", "docs": [ { "id": "lpc", "title": "LPC · Latency & Performance Canon", "path": "../panel/data/lpc.md", "phase": "phase-05", "layer": "latency_performance", "role": "Primary latency budget authority.", "fits": "Owns latency model, fallback rules and performance law.", "depends_on": [ "cfc" ], "used_by": [], "architecture_view": "Performance governance authority.", "label": "LPC · Latency & Performance Canon", "type": "text" } ], "phase_id": "phase-05", "subcategories": [ { "id": "prerequisites", "label": "prerequisites", "status": "MISSING", "buckets": [] }, { "id": "installation", "label": "installation", "status": "MISSING", "buckets": [] }, { "id": "configuration", "label": "configuration", "status": "MISSING", "buckets": [] }, { "id": "validation", "label": "validation", "status": "MISSING", "buckets": [] }, { "id": "observable_evidence", "label": "observable_evidence", "status": "MISSING", "buckets": [] }, { "id": "failure_modes_recovery", "label": "failure_modes_recovery", "status": "MISSING", "buckets": [] }, { "id": "completion_promotion", "label": "completion_promotion", "status": "MISSING", "buckets": [] } ] }, { "id": "noise_reduction", "title": "Noise Reduction Canon", "sub": "signal preservation, redundancy elimination and hop reduction.", "badge": "phase 06", "docs": [ { "id": "nrc", "title": "NRC · Noise Reduction Canon", "path": "../panel/data/nrc.md", "phase": "phase-06", "layer": "noise_reduction", "role": "Primary noise reduction authority.", "fits": "Owns anti-redundancy and anti-waste architectural guidance.", "depends_on": [ "lpc", "cfc" ], "used_by": [], "architecture_view": "Path simplification authority.", "label": "NRC · Noise Reduction Canon", "type": "text" } ], "phase_id": "phase-06", "subcategories": [ { "id": "prerequisites", "label": "prerequisites", "status": "MISSING", "buckets": [] }, { "id": "installation", "label": "installation", "status": "MISSING", "buckets": [] }, { "id": "configuration", "label": "configuration", "status": "MISSING", "buckets": [] }, { "id": "validation", "label": "validation", "status": "MISSING", "buckets": [] }, { "id": "observable_evidence", "label": "observable_evidence", "status": "MISSING", "buckets": [] }, { "id": "failure_modes_recovery", "label": "failure_modes_recovery", "status": "MISSING", "buckets": [] }, { "id": "completion_promotion", "label": "completion_promotion", "status": "MISSING", "buckets": [] } ] }, { "id": "observability_audit", "title": "Observability & Audit Canon", "sub": "documentation-facing audit model, evidence traceability and observability control, including distribution/package failure visibility, with runtime audit delegated to the Operator Panel.", "badge": "phase 07", "docs": [ { "id": "oac", "title": "OAC · Observability & Audit Canon", "path": "../panel/data/oac.md", "phase": "phase-07", "layer": "observability_audit", "role": "Primary observability and audit authority for the documentation side.", "fits": "Owns evidence traceability, audit-linked visibility, distribution/package failure visibility and the canonical audit model expected by runtime operations.", "depends_on": [ "cfc", "sec" ], "used_by": [], "architecture_view": "Documentation-side audit canon and observability authority, including distribution failure visibility.", "label": "OAC · Observability & Audit Canon", "type": "text" }, { "id": "panel_runtime_bridge", "title": "Panel Runtime Bridge", "path": "../panel/data/panel_runtime_bridge.json", "phase": "phase-04", "layer": "observability_audit", "role": "Runtime bridge authority.", "fits": "Connects canonical runtime expectations to observable runtime support artifacts.", "depends_on": [ "panel_data_contract", "panel_sync_contract" ], "used_by": [], "architecture_view": "Runtime bridge support layer.", "label": "Panel Runtime Bridge", "type": "json" }, { "id": "host_runtime_support", "title": "Host Runtime Support", "path": "../panel/data/host_runtime.json", "phase": "phase-04", "layer": "observability_audit", "role": "Runtime support artifact.", "fits": "Observable host runtime support record.", "depends_on": [ "panel_runtime_bridge" ], "used_by": [], "architecture_view": "Host runtime support evidence.", "label": "Host Runtime Support", "type": "json" }, { "id": "docker_runtime_support", "title": "Docker Runtime Support", "path": "../panel/data/docker_runtime.json", "phase": "phase-04", "layer": "observability_audit", "role": "Runtime support artifact.", "fits": "Observable docker runtime support record.", "depends_on": [ "panel_runtime_bridge" ], "used_by": [], "architecture_view": "Docker runtime support evidence.", "label": "Docker Runtime Support", "type": "json" }, { "id": "runtime_status_support", "title": "Runtime Status Support", "path": "../panel/data/runtime_status.json", "phase": "phase-04", "layer": "observability_audit", "role": "Runtime support artifact.", "fits": "Observable pipeline/runtime status support record.", "depends_on": [ "panel_runtime_bridge" ], "used_by": [], "architecture_view": "Runtime status support evidence.", "label": "Runtime Status Support", "type": "json" }, { "id": "runtime_row_semantics", "title": "Runtime Row Semantics Canonical", "path": "../panel/data/runtime_row_semantics_canonical.json", "phase": "phase-07", "layer": "observability_audit", "role": "Canonical semantic typing contract for every runtime row published by Devon.", "fits": "Defines row_kind, semantic_scope and completion eligibility rules for runtime rows.", "depends_on": [ "oac", "panel_runtime_bridge" ], "used_by": [], "architecture_view": "Runtime row semantic contract authority.", "label": "Runtime Row Semantics Canonical", "type": "json" } ], "phase_id": "phase-07", "subcategories": [ { "id": "prerequisites", "label": "prerequisites", "status": "MISSING", "buckets": [] }, { "id": "installation", "label": "installation", "status": "MISSING", "buckets": [] }, { "id": "configuration", "label": "configuration", "status": "MISSING", "buckets": [] }, { "id": "validation", "label": "validation", "status": "MISSING", "buckets": [] }, { "id": "observable_evidence", "label": "observable_evidence", "status": "MISSING", "buckets": [] }, { "id": "failure_modes_recovery", "label": "failure_modes_recovery", "status": "MISSING", "buckets": [] }, { "id": "completion_promotion", "label": "completion_promotion", "status": "MISSING", "buckets": [] } ] }, { "id": "security_governance", "title": "Security Canon", "sub": "security governance authority plus structured implementation artifacts, including environment-specific memory/data exposure policy and operator/runtime/debug separation.", "badge": "phase 08", "docs": [ { "id": "sec", "title": "SEC · Security Canon", "path": "../panel/data/sec.md", "phase": "phase-08", "layer": "security_governance", "role": "Primary security governance authority.", "fits": "Owns trust model, access control, memory protection, environment-specific memory/data exposure policy, operator/runtime/debug separation and security monitoring expectations.", "depends_on": [ "master_architecture_index" ], "used_by": [ "host_security", "app_security", "module_security", "runtime_security", "delivery_security", "approval_policy", "memory_isolation", "security_monitoring" ], "architecture_view": "Sovereign security meaning with environment exposure boundaries.", "label": "SEC · Security Canon", "type": "text" }, { "id": "host_security", "title": "Host Security Canonical", "path": "../panel/data/host_security_canonical.json", "phase": "phase-08", "layer": "security_governance", "role": "Structured host security implementation.", "fits": "Machine-readable host security canon.", "depends_on": [ "sec" ], "used_by": [], "architecture_view": "Host security implementation layer.", "label": "Host Security Canonical", "type": "json" }, { "id": "app_security", "title": "App Security Canonical", "path": "../panel/data/app_security_canonical.json", "phase": "phase-08", "layer": "security_governance", "role": "Structured app security implementation.", "fits": "Machine-readable application security canon.", "depends_on": [ "sec" ], "used_by": [], "architecture_view": "Application security implementation layer.", "label": "App Security Canonical", "type": "json" }, { "id": "module_security", "title": "Module Security Canonical", "path": "../panel/data/module_security_canonical.json", "phase": "phase-08", "layer": "security_governance", "role": "Structured module security implementation.", "fits": "Machine-readable module security canon.", "depends_on": [ "sec" ], "used_by": [], "architecture_view": "Module security implementation layer.", "label": "Module Security Canonical", "type": "json" }, { "id": "runtime_security", "title": "Runtime Security Canonical", "path": "../panel/data/runtime_security_canonical.json", "phase": "phase-08", "layer": "security_governance", "role": "Structured runtime security implementation.", "fits": "Machine-readable runtime security canon.", "depends_on": [ "sec" ], "used_by": [], "architecture_view": "Runtime security implementation layer.", "label": "Runtime Security Canonical", "type": "json" }, { "id": "delivery_security", "title": "Delivery Security Canonical", "path": "../panel/data/delivery_security_canonical.json", "phase": "phase-08", "layer": "security_governance", "role": "Structured delivery security implementation.", "fits": "Machine-readable delivery security canon.", "depends_on": [ "sec" ], "used_by": [], "architecture_view": "Delivery security implementation layer.", "label": "Delivery Security Canonical", "type": "json" }, { "id": "approval_policy", "title": "Approval Canonization Policy", "path": "../panel/data/approval_canonization_policy.json", "phase": "phase-08", "layer": "security_governance", "role": "Structured approval and canonization policy.", "fits": "Machine-readable approval guardrails.", "depends_on": [ "sec" ], "used_by": [], "architecture_view": "Approval policy implementation layer.", "label": "Approval Canonization Policy", "type": "json" }, { "id": "memory_isolation", "title": "Memory Isolation Canonical", "path": "../panel/data/memory_isolation_canonical.json", "phase": "phase-08", "layer": "security_governance", "role": "Structured memory isolation canon.", "fits": "Machine-readable memory partition and isolation rules.", "depends_on": [ "sec" ], "used_by": [], "architecture_view": "Memory isolation implementation layer.", "label": "Memory Isolation Canonical", "type": "json" }, { "id": "security_monitoring", "title": "Security Monitoring Canonical", "path": "../panel/data/security_monitoring_canonical.json", "phase": "phase-08", "layer": "security_governance", "role": "Structured security monitoring canon.", "fits": "Machine-readable security monitoring rules.", "depends_on": [ "sec" ], "used_by": [], "architecture_view": "Security monitoring implementation layer.", "label": "Security Monitoring Canonical", "type": "json" } ], "phase_id": "phase-08", "subcategories": [ { "id": "prerequisites", "label": "prerequisites", "status": "MISSING", "buckets": [] }, { "id": "installation", "label": "installation", "status": "MISSING", "buckets": [] }, { "id": "configuration", "label": "configuration", "status": "MISSING", "buckets": [] }, { "id": "validation", "label": "validation", "status": "MISSING", "buckets": [] }, { "id": "observable_evidence", "label": "observable_evidence", "status": "MISSING", "buckets": [] }, { "id": "failure_modes_recovery", "label": "failure_modes_recovery", "status": "MISSING", "buckets": [] }, { "id": "completion_promotion", "label": "completion_promotion", "status": "MISSING", "buckets": [] } ] }, { "id": "operational_flows", "title": "Operational Flows Canon", "sub": "documentation-facing operational sequence, runtime flow order and end-to-end action routing with real execution audit delegated to the Operator Panel.", "badge": "phase 09", "docs": [ { "id": "ofc", "title": "OFC · Operational Flows Canon", "path": "../panel/data/ofc.md", "phase": "phase-09", "layer": "operational_flows", "role": "Primary operational flow authority for the documentation side.", "fits": "Owns canonical operational sequence and ordered runtime flow expectations, while real execution audit remains operational.", "depends_on": [ "cfc", "sts" ], "used_by": [], "architecture_view": "Documentation-side operational flow authority.", "label": "OFC · Operational Flows Canon", "type": "text" } ], "phase_id": "phase-09", "subcategories": [ { "id": "prerequisites", "label": "prerequisites", "status": "MISSING", "buckets": [] }, { "id": "installation", "label": "installation", "status": "MISSING", "buckets": [] }, { "id": "configuration", "label": "configuration", "status": "MISSING", "buckets": [] }, { "id": "validation", "label": "validation", "status": "MISSING", "buckets": [] }, { "id": "observable_evidence", "label": "observable_evidence", "status": "MISSING", "buckets": [] }, { "id": "failure_modes_recovery", "label": "failure_modes_recovery", "status": "MISSING", "buckets": [] }, { "id": "completion_promotion", "label": "completion_promotion", "status": "MISSING", "buckets": [] } ] }, { "id": "delivery_layer", "title": "Delivery Layer", "sub": "build progression, release logic, pipeline mapping and operational content indexing.", "badge": "phase 09 / phase 02", "docs": [ { "id": "subcategory_pipelines", "title": "Subcategory Pipelines", "path": "../panel/data/subcategory_pipelines.json", "phase": "phase-09", "layer": "delivery_layer", "role": "Structured delivery pipeline authority.", "fits": "Defines subcategory pipeline sequence for operational surfaces.", "depends_on": [ "ofc" ], "used_by": [], "architecture_view": "Delivery pipeline support layer.", "label": "Subcategory Pipelines", "type": "json" }, { "id": "panel_content_index", "title": "Panel Content Index", "path": "../panel/data/panel_content_index.json", "phase": "phase-09", "layer": "delivery_layer", "role": "Structured panel content index authority.", "fits": "Defines stage-to-content mapping for the Operator Panel.", "depends_on": [ "master_architecture_index" ], "used_by": [], "architecture_view": "Content-index support layer.", "label": "Panel Content Index", "type": "json" } ], "phase_id": "phase-09", "subcategories": [ { "id": "prerequisites", "label": "prerequisites", "status": "MISSING", "buckets": [] }, { "id": "installation", "label": "installation", "status": "MISSING", "buckets": [] }, { "id": "configuration", "label": "configuration", "status": "MISSING", "buckets": [] }, { "id": "validation", "label": "validation", "status": "MISSING", "buckets": [] }, { "id": "observable_evidence", "label": "observable_evidence", "status": "MISSING", "buckets": [] }, { "id": "failure_modes_recovery", "label": "failure_modes_recovery", "status": "MISSING", "buckets": [] }, { "id": "completion_promotion", "label": "completion_promotion", "status": "MISSING", "buckets": [] } ] }, { "id": "memory_learning_reasoning", "title": "Memory, Learning & Reasoning Governance", "sub": "trust-bound memory, learning and reasoning expansion activated from Phase 08 and maintained as post-core canonical expansion.", "badge": "phase 08 / post-core", "docs": [ { "id": "memory_arch", "title": "Memory Canonical Architecture", "path": "../panel/data/memory_canonical_architecture.json", "phase": "phase-08", "layer": "memory_learning_reasoning", "role": "Structured memory architecture canon.", "fits": "Machine-readable memory architecture baseline.", "depends_on": [ "master_architecture_index" ], "used_by": [], "architecture_view": "Memory architecture support layer.", "label": "Memory Canonical Architecture", "type": "json" }, { "id": "memory_lifecycle", "title": "Memory Lifecycle Canonical", "path": "../panel/data/memory_lifecycle_canonical.json", "phase": "phase-08", "layer": "memory_learning_reasoning", "role": "Structured memory lifecycle canon.", "fits": "Machine-readable consolidation and lifecycle rules.", "depends_on": [ "master_architecture_index" ], "used_by": [], "architecture_view": "Memory lifecycle support layer.", "label": "Memory Lifecycle Canonical", "type": "json" }, { "id": "learning_gov", "title": "Learning Governance Canonical", "path": "../panel/data/learning_governance_canonical.json", "phase": "phase-08", "layer": "memory_learning_reasoning", "role": "Structured learning governance canon.", "fits": "Machine-readable learning guardrails.", "depends_on": [ "master_architecture_index" ], "used_by": [], "architecture_view": "Learning governance support layer.", "label": "Learning Governance Canonical", "type": "json" }, { "id": "planning_reasoning", "title": "Planning Reasoning Canonical", "path": "../panel/data/planning_reasoning_canonical.json", "phase": "phase-08", "layer": "memory_learning_reasoning", "role": "Structured planning and reasoning canon.", "fits": "Machine-readable planning and reasoning boundaries.", "depends_on": [ "master_architecture_index" ], "used_by": [], "architecture_view": "Planning governance support layer.", "label": "Planning Reasoning Canonical", "type": "json" }, { "id": "tool_execution", "title": "Tool Execution Canonical", "path": "../panel/data/tool_execution_canonical.json", "phase": "phase-08", "layer": "memory_learning_reasoning", "role": "Structured tool execution canon.", "fits": "Machine-readable permission and execution boundaries.", "depends_on": [ "master_architecture_index" ], "used_by": [], "architecture_view": "Tool execution governance support layer.", "label": "Tool Execution Canonical", "type": "json" }, { "id": "knowledge_ingestion", "title": "Knowledge Ingestion Canonical", "path": "../panel/data/knowledge_ingestion_canonical.json", "phase": "phase-08", "layer": "memory_learning_reasoning", "role": "Structured knowledge ingestion canon.", "fits": "Machine-readable ingestion and indexing boundaries.", "depends_on": [ "master_architecture_index" ], "used_by": [], "architecture_view": "Knowledge ingestion support layer.", "label": "Knowledge Ingestion Canonical", "type": "json" } ], "phase_id": "phase-08", "subcategories": [ { "id": "prerequisites", "label": "prerequisites", "status": "MISSING", "buckets": [] }, { "id": "installation", "label": "installation", "status": "MISSING", "buckets": [] }, { "id": "configuration", "label": "configuration", "status": "MISSING", "buckets": [] }, { "id": "validation", "label": "validation", "status": "MISSING", "buckets": [] }, { "id": "observable_evidence", "label": "observable_evidence", "status": "MISSING", "buckets": [] }, { "id": "failure_modes_recovery", "label": "failure_modes_recovery", "status": "MISSING", "buckets": [] }, { "id": "completion_promotion", "label": "completion_promotion", "status": "MISSING", "buckets": [] } ] }, { "id": "monitoring_observability", "title": "Monitoring & Real-time Observability", "sub": "real-time host, container and service monitoring canon with SSE bridge authority.", "badge": "phase 10", "docs": [ { "id": "monitoring_canonical", "title": "Monitoring Canonical", "path": "../panel/data/monitoring_canonical.json", "phase": "phase-10", "layer": "monitoring_observability", "role": "Primary real-time monitoring authority.", "fits": "Defines all monitoring targets, metrics, alert thresholds and refresh intervals.", "depends_on": [ "master_architecture_index" ], "used_by": [ "sse_bridge_canonical" ], "architecture_view": "Sovereign monitoring authority for host, containers and services.", "label": "Monitoring Canonical", "type": "json" }, { "id": "sse_bridge_canonical", "title": "SSE Bridge Canonical", "path": "../panel/data/sse_bridge_canonical.json", "phase": "phase-10", "layer": "monitoring_observability", "role": "SSE transport authority replacing push_snapshot model.", "fits": "Defines the permanent SSE channel from Devon to Waresite Operator Panel.", "depends_on": [ "monitoring_canonical" ], "used_by": [], "architecture_view": "SSE bridge transport authority.", "label": "SSE Bridge Canonical", "type": "json" } ], "phase_id": "phase-10", "subcategories": [ { "id": "prerequisites", "label": "prerequisites", "status": "MISSING", "buckets": [] }, { "id": "installation", "label": "installation", "status": "MISSING", "buckets": [] }, { "id": "configuration", "label": "configuration", "status": "MISSING", "buckets": [] }, { "id": "validation", "label": "validation", "status": "MISSING", "buckets": [] }, { "id": "observable_evidence", "label": "observable_evidence", "status": "MISSING", "buckets": [] }, { "id": "failure_modes_recovery", "label": "failure_modes_recovery", "status": "MISSING", "buckets": [] }, { "id": "completion_promotion", "label": "completion_promotion", "status": "MISSING", "buckets": [] } ] } ], "canon_meta": { "canonical_hierarchy": [ "phase", "category", "subcategory", "bucket", "item" ] } }