> **Operator reference:** This page documents internal estate coordination across `starlight/repos`. Looking for customer and developer documentation? Start at [What you can do with Starlight](/starlight/overview) or the [MCP quickstart](/starlight/quickstart).

## The three planes [#the-three-planes]

1. **Machine plane.** Workstation health, the shared CDP browser multiplexer (`localhost:9223`), and scheduled Windows watchdogs (`StarlightHorizon2h/12h/1w`, `StarlightTaskHealthWatch`).
2. **Repo plane.** Canonical repositories under `starlight/repos`. `starlight-agent-config/core/doctrine/SYSTEM-SPINE.md` holds the compiled doctrine spine projected into each harness (`CLAUDE.md`, `AGENTS.md`, `GEMINI.md`).
3. **Memory plane.** The six semantic vaults in `Starlight-Intelligence-System/memory/vaults/` (Strategic, Technical, Creative, Operational, Wisdom, Horizon) served locally by `SisGatewayDaemon` (`127.0.0.1:5200`).

## Where each operator question resolves [#where-each-operator-question-resolves]

| Question | Canonical source |
|---|---|
| What is ruled vs. measured vs. open right now? | `starlight/TRUTH.md` and `ops/DIRECTIVE_LEDGER.jsonl` |
| What are the ranked objectives (O1–O7)? | `starlight/OBJECTIVES.md` |
| Which repo and brand owns a surface? | `starlight/ecosystem.json` and `PROPERTIES-REGISTRY.md` |
| Which harness owns an active branch or worktree? | `tools/lane.mjs` and `agentic-ops-hub/ops/OPS-LEDGER.md` |
| Did a different harness review this PR? | `node tools/pr-gate.mjs verify --repo <owner/name> --pr <N>` |

## One writer per lane [#one-writer-per-lane]

Multiple coding agents operate across the estate concurrently. Every write lane works on an isolated branch (`agent/<harness>/<scope>` or `codex/<scope>`), and no PR merges without a cross-harness sign-off bound to the exact head SHA via `tools/pr-gate.mjs`.