Implementation plan — Excititor

Current objectives

  • Maintain deterministic behaviour and offline parity across releases.
  • Keep documentation, telemetry, and runbooks aligned with the latest sprint outcomes.

Workstreams

  • Backlog grooming: reconcile open stories in …/…/TASKS.md with this module’s roadmap.
  • Implementation: collaborate with service owners to land feature work defined in SPRINTS/EPIC docs.
  • Validation: extend tests/fixtures to preserve determinism and provenance requirements.

Epic milestones

  • Epic 1 – AOC enforcement: enforce immutable VEX observation schema, provenance capture, and guardrails.
  • Epic 7 – VEX Consensus Lens: provide lens-ready metadata (issuer trust, temporal scoping) and consensus APIs.
  • Epic 8 – Advisory AI: guarantee citation-ready payloads and normalized context for AI summaries/explainers.
  • Track DOCS-LNM-22-006/007 and CLI-EXC-25-001…002 in …/…/TASKS.md.

Coordination

  • Review ./AGENTS.md before picking up new work.
  • Sync with cross-cutting teams noted in /docs/implplan/SPRINT_*.md.
  • Update this plan whenever scope, dependencies, or guardrails change.

Sprint alignment (2025-11-07)

Sprint taskState (SPRINT_200)Notes
EXCITITOR-DOCS-0001DONEREADME release alignment + consensus beta references refreshed (DSSE/export guidance).
EXCITITOR-ENG-0001DONEImplementation plan now mirrors SPRINT_200_documentation_process.md through this table.
EXCITITOR-OPS-0001DONERunbook/observability checklist added to docs/modules/excititor/mirrors.md.

See /docs/implplan/SPRINT_200_documentation_process.md for the canonical status table.