> Historical July 11, 2026 planning record. Public copy redacted September 17, 2026 to remove operational details; original retained privately. This is not current operational status. # 048-DR-INDEX — Mission Control glossary > **What this is and why it matters.** A small document that becomes priceless later. When > several people and agents work on a platform for years, the same word quietly comes to mean > different things to different readers — and plans built on ambiguous terms drift. This defines > the load-bearing vocabulary of Mission Control once, so every other document and every future > contributor uses the words the same way. Terms are grouped, then listed A–Z within each group; > where a term is a formal data entity it points at the schema that defines it. - **Program:** Mission Control (constitution: `038-AT-DECR`) - **Rule:** if a document uses one of these terms in a different sense, the document is wrong, not the glossary — fix the document or amend the glossary here (never fork the meaning). --- ## Core platform terms - **Intent OS** — the private repository and the operational control plane of record for Intent Solutions. Both the code/docs home and, increasingly, the running platform. (ADR-000 §1.) - **Mission Control** — the platform Intent OS is becoming: the authoritative control plane for running every product, ending in an authenticated web application with role-based access. - **Platform service** — a capability exposed through a stable internal interface (an API or a queryable data model), such that the portal is a UI over it rather than a rewrite. The unit the whole program is organized around. (ADR-000 §4.1.) - **Capability** — a thing the platform can do (backups, incidents, deployments, monitoring, AI-agent management…). A capability is realized as one or more platform services. - **Schema** — a versioned data contract (a JSON Schema) defining the shape of a data entity other components read or write. The canonical anti-drift mechanism. (`037` Epic 1.4.) ## Estate / infrastructure terms - **Estate** — every piece of Intent Solutions infrastructure across every machine, taken together. - **Environment** — a named context a service runs in (Production, Development). A formal entity in the Service/Host/Environment schema. [Operational detail retained in the private record] - **Service** — a running application or component with an interface (a container, a systemd unit, an API). A formal entity keyed by a stable ID that everything else joins on. - **Stack** — one `docker compose` project: a group of containers making up one application. [Operational detail retained in the private record] ## Operations terms - **Automation** — a scheduled, unattended job (a cron entry, a systemd timer, a CI schedule): a sweep, a watchdog, a backup, a deploy pipeline. Tracked in the automations registry. - **Agent** — an autonomous or semi-autonomous actor (an AI agent / governed background agent, a scheduled Claude routine). An agent is a *governed actor* that calls platform services under the same integration contract as any other capability. A subtype of automation in the data model. - **Runbook** — a document telling a human or agent **how to operate** a capability day-to-day. - **Playbook** — a runbook for a **specific failure mode** (what to do when X breaks). - **Incident** — a formal record of a service disruption, with a lifecycle: open → acknowledge → resolve, plus a timeline. A data entity (`037` Epic 1.4b), distinct from a raw alert. - **Alert** — a single notification that something crossed a threshold. Many alerts may belong to one incident. Delivered through the notify spine. - **Recovery** — restoring a capability or its data after a failure. **Data recovery** (restore from backup) and **host recovery** (rebuild the machine) are distinct; disaster recovery (DR) needs both. - **Action** — a privileged operation the platform performs or enqueues (deploy, kill, rollback, secret-decrypt). Every action emits an append-only audit event. (ADR-000 amendment C19.) ## Program / governance terms - **Program** — the whole multi-phase effort to build Mission Control. - **Phase** — one milestone in the program (Phase 0 planning; Phases 1–3 implementation). A phase is a stable foundation for the next. (ADR-000 Article I.) - **Epic** — a cluster of related work delivering one capability; tracked as a parent bead + a GitHub cluster issue. - **Bead** — one tracked unit of work in the `bd` task system; the source-of-truth task record, mirrored to a GitHub issue and (when applicable) a Plane issue. - **ADR** — Architecture Decision Record: a durable record of a significant decision and why. ADR-000 is the program constitution; the ADR index is `047`. - **AAR** — After-Action Report: the mandatory 9-section record filed at every epic/phase close (`039`, template `000-AA-TMPL`). - **Integration contract** — the eight-plus clauses every capability signs up to (registered, observable, recoverable, deployable, tracked, documented, service-shaped, secret-safe, supported). ADR-000 §7. - **RPO / RTO** — Recovery Point Objective (max data age lost in a restore) / Recovery Time Objective (max time to restore). Stated per stack (`037` J8, `043`). - **MTTD / MTTR** — Mean Time To Detect / Mean Time To Recover. KPIs in `043`. - **The brain / governed knowledge base** — the Compile-Then-Govern knowledge system (governance engine plus search index) that compiles facts into audited memories queried with citations. - **Disclosure tiers** — the rule set governing what content may appear where (public / internal / private); no compensation or personal data anywhere in this repo or the brain. ## Governance rule New load-bearing terms are added here when they first appear in a deliverable; a term used in two senses is a defect to resolve, not a synonym to tolerate.