Skip to content

Status

CaseGraph is usable today as a local developer platform for provider-free workflows. Release artifacts are validated locally; PyPI publication is a separate operation.

Implemented

  • Top-level Python Developer API through from casegraph import EngineHost.
  • Package-first workflow bootstrap with casegraph init.
  • First workflow editing loop guidance in generated transactional packs.
  • First workflow inspection with casegraph cases inspect <case-id>.
  • Release-artifact validation for wheel, source distribution, installed CLI, packaged migrations, optional extras, and the installed first workflow.
  • Guarded PyPI/TestPyPI release workflow using PyPI Trusted Publishing through GitHub Actions OIDC.
  • Database readiness and migration commands with casegraph db check and casegraph db upgrade.
  • Transactional pack scaffolding with casegraph packs scaffold --kind transactional.
  • Pack validation and author-check loops.
  • Decorated native worker functions through @worker(...) and WorkerOutput.
  • Worker step capture through context.step(...).
  • Structured decision governance through cover.case(...) for typed cover.Decision outputs, multiple evidence records, and decorated local actions.
  • Minimal runtime coverage instrumentation through from casegraph import cover and with cover.run(...) for supported Pydantic-AI, LangChain, LangGraph, and OpenAI SDK calls.
  • Optional advanced Pydantic-AI worker-step instrumentation through casegraph[pydantic-ai].
  • Static existing-system inspection with casegraph cover inspect.
  • Draft read-only pack generation from inspection reports with casegraph cover scaffold.
  • Human-reviewed cover mapping apply with casegraph cover review template/status/apply.
  • Deterministic cover review suggestions with casegraph cover suggest.
  • Deterministic external-write boundary suggestions with casegraph cover boundaries suggest.
  • Reviewed transactional cover generation with casegraph cover boundaries review template/status/apply.
  • Dry-run external adapter stubs for reviewed cover transactional boundaries.
  • Adapter dry-run checks with casegraph packs adapter-dry-run.
  • Adapter preflight guardrails with casegraph packs adapter-preflight.
  • Opt-in real external adapter execution through Python EngineHost.commit(...) after reviewed policy, passing real preflight artifact, env gate, action/target allowlist, verification, and compensation coverage.
  • Inert real-adapter templates and a generated runbook for reviewed cover packs.
  • Helper-backed local/fake transactional capabilities for one deterministic action.
  • Helper-backed local/fake transactional capability sets for multiple independent actions.
  • Browser casefile inspection for support and generated/custom cases, including a generic execution report backed by the same read model as casegraph cases inspect.
  • Browser operator flow for explicitly registered generated/custom packs through CASEGRAPH_PACK_ROOTS.
  • Opt-in OpenAI model runs, model evals, and live cover.case(...) structured-decision dogfood.

Current Gaps

  • PyPI publication has not been performed.
  • PyPI Trusted Publisher configuration still has to be created on PyPI/TestPyPI before the first real publish.
  • Greenfield transactional scaffolds still start with one local/fake action.
  • Generated/custom browser execution requires explicit local pack registration before API startup; unregistered cases remain read-only in the browser.
  • Cover suggestions are deterministic hints; developers still have to review and promote mappings.
  • Runtime coverage artifacts from cover.run(...) are local capture records; use cover.case(...) when a structured decision should become governed CaseGraph evidence and a local committed outcome.
  • Generated cover packs remain dry-run by default; real templates still require developer-authored wiring.
  • There is no standalone real adapter run CLI. Real execution is intentionally tied to proposals, policy, approval, and commits through the Python Developer API.
  • Streaming runtime calls are marked but not consumed by coverage instrumentation yet.

Roadmap

The active milestone is a usability reset: make CaseGraph easy to try, edit, and debug as a first developer workflow before continuing deeper cover-agent work.

Usability 1A - Package-First Bootstrap and First Workflow Trial is complete.

Usability 1B - First Workflow Editing Loop is complete.

Usability 1C - First Project Debugging and Inspection is complete.

Package Distribution 1A - Release-Ready Install Path is complete.

Docs 2C - Package-First Release Narrative is complete.

Release Operations 1A - PyPI Publishing Guardrails is complete.

Browser Usability 1A - Generated Pack Casefile Fit is complete.

Browser Usability 1B - Generated Pack Operator Flow is complete.

Adapter Usability 1A - Unified Minimal Coverage Instrumentation is complete.

Cover Governance 1A - Structured Decision UX is complete.

The next product slice is Browser Usability 1C - Pack Registration Startup UX.

The direction is:

  1. keep the package-first path clear without claiming PyPI publication;
  2. require Trusted Publishing, protected environments, and release preflight before publication;
  3. reduce the API/web startup friction now that generated-pack browser execution works.

PLAN.md is the active roadmap. PLAN_ARCHIVE.md preserves historical completed slices and superseded build-order details.