Skip to content

Phase 2 — Architecture Plan

  • Date: 2026-08-02
  • Status: Approved and executed (2026-08-02). Approval recorded in Decisions.md, ADR-0004.
  • Phase: Phase 2 — Architecture

Objective

Turn the verified Phase 1B observations into an approved system architecture for a provider-aware statusline, satisfying the Roadmap Phase 2 gate: the data source for each displayed value is identified, and the design does not depend on unverified behavior.

Scope and constraints

  • Read-only by default. No edits to Claude Code configuration, OmniRoute, or the statusline (operating rule 5).
  • No live inference. No chat requests, no header-observation request.
  • Secrets. Nothing read from server.env, api_keys, or any credential store. The management-token question is treated as out of scope; the architecture assumes the HTTP management API is unavailable.
  • No dependency on unverified behavior. Where a value cannot be verified, the design does not depend on it — it is documented as an open item.
  • No implementation. Statusline code stays in Phase 4.

Workstreams

  • W1 — Architecture synthesis (Architecture.md): logical + physical data-flow diagrams, component responsibilities and trust boundaries, candidate integration options and tradeoffs, failure/fallback behavior, version-change behavior, data source per displayed value, statically-allowlisted read path.
  • W2 — Read-only verification of open questions: latency (transcript tail vs SQLite), resolved-model stability, transcript message.model reliability, freshness/staleness, provider inference. All read-only, no credential tables.
  • W3 — Architecture decision records (Decisions.md): ADRs for the material choices (primary data source, provider policy, correlation model, version-change handling), plus the plan approval record.
  • W4 — Documentation updates: Knowledge-Base.md open questions, Roadmap.md status, plan + findings recorded in Findings/.

Exclusions (needs separate approval, not in this plan)

  • Stopping/restarting the OmniRoute container to test down-behavior.
  • Any live request through the gateway (header observation).
  • Reading server.env / api_keys / admin UI to extract a management token.

Execution record

  • W2 ran as written. Observations: Findings/2026-08-02 - Phase 2 - Read-only Verification.md.
  • W1, W3, W4 completed. Deliverables: approved architecture in Architecture.md; decisions in Decisions.md ADR-0004–0008; knowledge base and roadmap updated.
  • ADR-0005–0008 are recorded as Proposed; acceptance is the Phase 2 completion review step.

Gate (from Roadmap, Phase 2)

Phase 2 completes when: every displayed value has an identified data source; nothing depends on unverified behavior (or it is explicitly marked); failure, timeout, privacy, and version-change behavior are documented; and the decision is recorded in Decisions.md.