Repo Shape

The repository is organized around a provider-neutral core plus narrow boundary packages.

Top-Level Layout

repo/
  docs/
  evals/
  packages/
    context_core/
    provider_openai/
    provider_anthropic/
    recorder/
    mcp_bridge/
    otel_export/
  services/
    api/
  apps/
    dashboard/
  examples/
    openai_context_demo/
    anthropic_coding_agent/
    langgraph_wrapper/
    mcp_ingest_demo/
  tests/
    unit/
    integration/
    fixtures/

Package Roles

• context_core: provider-neutral schemas, normalization, validation, compilation, and receipts
• provider_openai: first OpenAI adapter and demo-facing request/response models
• provider_anthropic: placeholder Anthropic adapter boundary
• recorder: persistence, receipts, diffs, and replay artifacts
• mcp_bridge: MCP-facing context ingestion boundary
• otel_export: optional telemetry export boundary
• services/api: FastAPI sidecar boundary

Examples

• openai_context_demo: current golden-path example
• anthropic_coding_agent: placeholder
• langgraph_wrapper: placeholder
• mcp_ingest_demo: placeholder

Long-Form Reference Docs

The architecture briefs are still valuable, but they are not the best first entrypoint for new readers:

• V1 Brief
• V2 Brief

Use those when you need the broader roadmap or earlier design rationale.

Evals

• evals/coding_continuation: offline harness for comparing transcript replay, compact summary, and StatePlane continuation context against explicit fixture ground truth