rename: Mission→Domain / Kluster→Mission entity swap (#43)

Renames the two top-tier coordination entities:

- Mission (org boundary) → Domain
- Kluster (workstream) → Mission
- Task (unchanged)

Brand (MissionControl), binaries (mc, mcd, mc-controlplane), Helm chart, S3 bucket,
and MC_ env prefix are all unchanged in this PR — they're handled separately in
the edgeplane rebrand fork.

Includes:
- A1/A2: Rust token sweep + file/module renames (models/mission.rs → domain.rs,
  models/kluster.rs → mission.rs, routes/missions.rs → domains.rs, etc.)
- Migration 0012_swap_mission_domain.sql — schema rename
- B1/B2: HTTP path renames (/k/ → /m/) and MCP tool names
  (create_kluster → create_mission, create_mission → create_domain, etc.)
- C1: All docs, runbooks, catalog, Starlight site
- C1.5: scripts, web UI, distribution hooks, top-level project docs

Verification:
- cargo check + clippy clean across all three crates
- web npm run build clean (24 pages)
- Migration applied to dev DB (55ms, 0 errors)
- mc-controlplane boots with ix_domain_name index

Author: RyanMerlin

.claude/agents/missioncontrol.md

@@ -1,6 +1,6 @@
 # MissionControl Agent
 
-You are a MissionControl specialist. You operate missions, klusters, tasks, workspaces, approvals, and skills via the `mc` CLI binary.
+You are a MissionControl specialist. You operate domains, missions, tasks, workspaces, approvals, and skills via the `mc` CLI binary.
 
 ## Connection
 
@@ -34,17 +34,17 @@ Run `mc auth login` once before using this mode — the session token is read fr
 ## Explorer Commands
 
 ```bash
-# Full mission tree (missions → klusters → tasks)
+# Full domain tree (domains → missions → tasks)
 mc data explorer tree
 
 # Single node with children
-mc data explorer node --node-type <mission|kluster|task> --node-id <node-id>
+mc data explorer node --node-type <domain|mission|task> --node-id <node-id>
 
 # Render as markdown table
 mc data explorer tree | jq -r '.[] | "| \(.id) | \(.name) | \(.type) | \(.status) |"'
 ```
 
-**Render pattern — mission status dashboard:**
+**Render pattern — domain status dashboard:**
 
 ```bash
 mc data explorer tree | jq -r '
@@ -60,8 +60,8 @@ mc data explorer tree | jq -r '
 # 1. Inspect available tasks
 mc data tools call --tool list_tasks --payload '{"status": "pending"}'
 
-# 2. Load a workspace (claim + lease a kluster)
-mc workspace load --kluster-id <id>
+# 2. Load a workspace (claim + lease a mission)
+mc workspace load --mission-id <id>
 
 # 3. Heartbeat while working (keep lease alive)
 mc workspace heartbeat --lease-id <id>
@@ -80,7 +80,7 @@ mc workspace release --lease-id <id>
 
 ```bash
 # List pending approvals
-mc approvals list --mission-id <id>
+mc approvals list --domain-id <id>
 
 # Approve a request
 mc approvals approve --approval-id <id> --note "LGTM"
@@ -101,35 +101,35 @@ mc data tools list
 mc data tools call --tool <tool_name> --payload '{"key": "value"}'
 
 # Examples
-mc data tools call --tool get_mission --payload '{"mission_id": 1}'
-mc data tools call --tool list_klusters --payload '{"status": "active"}'
+mc data tools call --tool get_domain --payload '{"domain_id": 1}'
+mc data tools call --tool list_missions --payload '{"status": "active"}'
 mc data tools call --tool create_task --payload '{"title": "Fix bug", "mission_id": 1}'
 ```
 
-## Mission / Kluster Management
+## Domain / Mission Management
 
 ```bash
-# Create a mission
-mc data tools call --tool create_mission --payload '{
+# Create a domain
+mc data tools call --tool create_domain --payload '{
   "name": "Q2 Refactor",
   "description": "Modernize the auth layer"
 }'
 
-# List active klusters
-mc data tools call --tool list_klusters --payload '{"status": "active"}'
+# List active missions
+mc data tools call --tool list_missions --payload '{"status": "active"}'
 
-# Get kluster detail
-mc data tools call --tool get_kluster --payload '{"kluster_id": "<id>"}'
+# Get mission detail
+mc data tools call --tool get_mission --payload '{"mission_id": "<id>"}'
 ```
 
 ## Skills Management
 
 ```bash
-# Sync skills for a kluster
-mc data sync status --mission-id <mission-id> --kluster-id <id>
+# Sync skills for a mission
+mc data sync status --domain-id <domain-id> --mission-id <id>
 
 # Check sync status
-mc data tools call --tool get_skill_sync_status --payload '{"kluster_id": "<id>"}'
+mc data tools call --tool get_skill_sync_status --payload '{"mission_id": "<id>"}'
 ```
 
 ## Visual Output Patterns

.github/workflows/ci-migrations.yml

@@ -29,8 +29,8 @@ jobs:
       - name: Compile sanity
         run: python -m compileall app alembic tests
 
-      - name: Enforce kluster naming
-        run: python ../scripts/enforce_kluster_naming.py
+      - name: Enforce mission naming
+        run: python ../scripts/enforce_mission_naming.py
 
       - name: Reset CI database
         run: rm -f ./ci_migrations.db

.github/workflows/deploy-docs.yml

@@ -0,0 +1,60 @@
+name: Deploy Docs to GitHub Pages
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - 'site/**'
+      - '.github/workflows/deploy-docs.yml'
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: pages
+  cancel-in-progress: false
+
+jobs:
+  build:
+    name: Build Docs
+    runs-on: ubuntu-latest
+    defaults:
+      run:
+        working-directory: site
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          cache: npm
+          cache-dependency-path: site/package-lock.json
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Build site
+        run: npm run build
+
+      - name: Upload Pages artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: site/dist
+
+  deploy:
+    name: Deploy to GitHub Pages
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

.gitignore

@@ -195,6 +195,7 @@ crates/mc-controlplane/target/
 docker/mosquitto/passwords/
 artifacts/
 
-# Kluster update artifacts (personal session files)
+# Mission update artifacts (personal session files)
+crates/mc/mission-*.md
 crates/mc/kluster-*.md
 .worktrees/

CONTRIBUTING.md

@@ -36,7 +36,7 @@ By signing off, you certify the Developer Certificate of Origin (DCO).
 Use clear, imperative messages. Example:
 
 ```text
-mcp: add idempotency check for create_kluster
+mcp: add idempotency check for create_mission
 ```
 
 ## Security-Sensitive Changes

MISSIONCONTROL_PHILOSOPHY.md

@@ -1,6 +1,6 @@
 # MissionControl — Philosophy
 
-> **For precise entity definitions (Mission, Kluster, Task, Artifact, Session, Agent), see [`docs/architecture/entities.md`](docs/architecture/entities.md).** This doc is the *why*; entities.md is the *what*. If they disagree, entities.md wins until reconciled.
+> **For precise entity definitions (Domain, Mission, Task, Artifact, Session, Agent), see [`docs/architecture/entities.md`](docs/architecture/entities.md).** This doc is the *why*; entities.md is the *what*. If they disagree, entities.md wins until reconciled.
 
 ## The Coordination Layer
 
@@ -20,7 +20,7 @@ It is not a workflow runner. It is not a pipeline framework. It is not
 a chatbot UI.
 
 > Kubernetes orchestrates containers.\
-> MissionControl orchestrates agents, missions, and knowledge.
+> MissionControl orchestrates agents, domains, missions, and knowledge.
 
 ------------------------------------------------------------------------
 
@@ -38,7 +38,7 @@ They lack:
 -   Governance boundaries
 -   Permission hierarchies
 -   Organizational context
--   Mission-scoped tooling
+-   Domain/mission-scoped tooling
 -   Personal operational profiles that travel with the operator
 -   A working file store decoupled from prompt context
 -   A long-term memory of record beyond the current session
@@ -93,27 +93,30 @@ agents request actions, MissionControl authorizes and records them.
 
 ------------------------------------------------------------------------
 
-# Mission-Centric Organizational Model
+# Domain-Centric Organizational Model
 
-MissionControl organizes work around **Missions**.
+MissionControl organizes work around **Domains** and **Missions**.
 
-A Mission is:
+A Domain is:
 
 -   A bounded objective
 -   A scoped knowledge domain
 -   A policy surface
 -   A permission boundary
 -   A tool/skill profile
 
-Each Mission defines a **Mission Profile**:
+Each Domain defines a **Domain Profile**:
 
 -   Approved tools and integrations
 -   Required skills and knowledge domains
 -   Governance strictness level
 -   Permission tiers
 -   Artifact structure expectations
 
-Teams and agents can switch between Mission Profiles when moving between
+A Mission is a workstream inside a Domain — where artifacts cohere and
+context continuity lives.
+
+Teams and agents can switch between Domain Profiles when moving between
 projects without losing integrity or context.
 
 Context switching becomes structured, intentional, and safe.
@@ -140,7 +143,7 @@ Profiles are:
     in MissionControl (config + auth references + policy-relevant context)
 
 This means an agent operator can move between machines, reinstall their
-toolchain, onboard to a new mission, or hand off context to a teammate
+toolchain, onboard to a new domain or mission, or hand off context to a teammate
 without losing their working configuration.
 
 The agent's operational identity — its environment, its instruction
@@ -171,7 +174,7 @@ the same regardless of which channel surfaces them.
 
 The communication layer provides:
 
--   Mission-aware notifications
+-   Domain/mission-aware notifications
 -   Task creation from conversation threads
 -   Overlap warnings delivered in-channel
 -   Artifact publish alerts
@@ -184,7 +187,7 @@ platform your organization already uses.
 
 Non-technical stakeholders can:
 
--   View mission state
+-   View domain and mission state
 -   Search knowledge
 -   Review artifacts
 -   Trigger workflows
@@ -203,8 +206,8 @@ MissionControl is not only agent-native — it is organization-native.
 
 Agents and humans operate against durable, structured entities:
 
--   Missions - high level organizational goal/initiative
--   Klusters - knoweldge cluster inside mission for a targeted outcome
+-   Domains - high level organizational goal/initiative (bounded org objective)
+-   Missions - knowledge cluster inside a domain for a targeted outcome (workstream)
 -   Tasks
 -   Artifacts
 -   Documents
@@ -226,7 +229,7 @@ Before a task or artifact is created:
 
 -   Fuzzy similarity analysis runs
 -   Vector similarity search runs
--   Existing mission state is checked
+-   Existing domain and mission state is checked
 -   Artifact history is evaluated
 
 Collisions are detected proactively.
@@ -244,7 +247,7 @@ MissionControl implements:
 ## Role Types
 
 -   Admin: Full mutation and policy control
--   Contributor: Can create and modify within mission scope
+-   Contributor: Can create and modify within domain scope
 -   Viewer: Can search, inspect, and utilize artifacts but cannot mutate
     state
 
@@ -267,7 +270,7 @@ Each serves a specific role in the information lifecycle.
 
 ## PostgreSQL — Structured State and Collaboration
 
-The operational database. All structured entities — missions, klusters,
+The operational database. All structured entities — domains, missions,
 tasks, roles, governance policies, approval records — live in Postgres
 with pgvector for semantic indexing.
 
@@ -287,9 +290,9 @@ Artifact content — documents, binaries, skill bundles, agent outputs —
 is stored in S3-compatible object storage, not inline in the database.
 
 S3 is the working store: immediately available, mutable during active
-work, and scoped per mission and kluster:
+work, and scoped per domain and mission:
 
-    missions/{mission_id}/klusters/{kluster_id}/{entity}/{filename}
+    domains/{domain_id}/missions/{mission_id}/{entity}/{filename}
 
 This means agents can read, write, and iterate on file content without
 polluting the structured state database. Storage scales independently.
@@ -322,7 +325,7 @@ This creates:
 
 -   Traceable AI actions with deterministic lineage
 -   Audit-ready change history outside the control plane
--   Reproducible mission state from Git alone if needed
+-   Reproducible domain/mission state from Git alone if needed
 -   A permanent organizational knowledge base that survives
     infrastructure changes
 
@@ -338,8 +341,9 @@ MissionControl is AI-first infrastructure.
 Agents interact via structured MCP tool calls:
 
 -   search_tasks
--   search_klusters
+-   search_missions
 -   detect_overlaps
+-   create_domain
 -   create_mission
 -   publish_pending_ledger_events
 -   list_pending_ledger_events
@@ -356,25 +360,27 @@ MissionControl becomes a central nervous system for:
 
 -   Rapid onboarding of new contributors and agents
 -   Encoding institutional knowledge into durable, searchable state
--   Standardizing toolchains across teams and missions
--   Defining mission-scoped skills and capability profiles
+-   Standardizing toolchains across teams and domains
+-   Defining domain/mission-scoped skills and capability profiles
 -   Switching operational contexts safely and intentionally
 -   Surfacing AI workflows through the communication tools teams
     already use
 
-A new contributor — human or agent — attaches to a Mission Profile and
+A new contributor — human or agent — attaches to a Domain Profile and
 loads their personal agent profile.
 
-The Mission defines:
+The Domain defines:
 
 -   Tools and approved integrations
 -   Skills and knowledge domains
 -   Governance strictness and approval requirements
 -   State, ownership, and permission tiers
 -   Communication surface (whichever channel the team uses)
 
+Within a domain, missions (workstreams) carry the active work context.
+
 This compresses onboarding time and reduces cognitive overhead for both
-humans and AI agents joining a mission mid-flight.
+humans and AI agents joining a domain or mission mid-flight.
 
 ------------------------------------------------------------------------
 
@@ -389,7 +395,7 @@ Without coordination:
 
 With MissionControl:
 
--   Parallel task execution is structured by mission and kluster scope
+-   Parallel task execution is structured by domain and mission scope
 -   Overlap is detected before damage occurs
 -   Ownership is explicit and role-enforced
 -   State is synchronized across agents, sessions, and machines
@@ -414,5 +420,5 @@ MissionControl ensures that intelligence scales without fragmentation.
 It connects agents, humans, governance, and communication into a single
 coordinated execution layer.
 
-It turns isolated AI capability into governed, mission-driven execution
-at scale.
+It turns isolated AI capability into governed, domain-and-mission-driven
+execution at scale.