Limitations
What's in this doc
The honest scope boundary for the 0.2.0 MVP release line. What's
end-to-end production-ready today, what exists as contract/helper
scaffolding, what's deliberately deferred, and how the v0.x release
posture is framed.
End-to-end versus contract.
The repository has broad contract, helper, CLI, and documentation coverage through the v0.12 roadmap — but several surfaces are not yet end-to-end production workflows. This doc draws the line.
Current end-to-end surfaces
The pieces below ship as user-facing workflows with persistence, docs, tests, and CI coverage.
Local home & store
Initialization, layout, override via CRAIK_HOME.
Project registration
Add, list, inspect projects. Task creation.
Case-file assembly
From local repo state plus optional read-only GitHub context.
Local artifacts
Receipts, handoffs, memory proposals, contradictions, work-graph inspection.
Policy
Profile generation, capability-grant checks, regression tests.
Stigmem reads
Compatibility detection and policy-gated direct fact write helpers.
Fixture loop
Deterministic fixture loop and runner preview contracts.
Provider paths
Fixture-backed and live opt-in OpenAI Responses, Anthropic Messages, and OAI-compatible Chat Completions.
OIDC login
Device-code and loopback+PKCE flows.
Credential sources
Env-var API keys, local-CLI OAuth fallback, vendor-CLI bridges, secret references, markers, Stigmem-backed references.
Credential pools
Failover and per-profile health tracking.
Identity on receipts
Operator and credential identity on every provider receipt.
Policy-bound credentials
Operators and credentials constrained by policy.
Approval-gated first use
First live use of a credential requires explicit approval.
Resumable runs
Provider-backed runs persist phase outputs and idempotency keys so interrupted runs can resume from durable boundaries.
Budget enforcement
Wall-clock, provider-token, and pre-dispatch time checks interrupt exhausted runs before additional calls or side effects.
Local-process sandbox
Registered shell command references can execute through the local-process sandbox backend with cancellation propagation.
Run recovery views
craik run show, craik run resume, craik run cancel, and craik run delta expose continuity state.
Store migrations
Local-store schema changes run through a registered, forward-only migration framework.
Stigmem docs demo
The accepted release-acceptance workflow.
Contract or helper surfaces
These surfaces ship as typed contracts, evaluators, formatters, or fixtures — useful, but not yet operational workflows.
live_enabled=true on ProviderRuntimeConfig plus a resolved credential. CI does not exercise paid live providers.Known MVP gaps
Scheduled milestones with explicit version targets.
Other near-term deferrals: remote Stigmem write promotion after proposal review · god-file cleanup and runtime sub-packaging before the MVP freeze · ADR-backed design decisions for runner scope, release posture, and package boundaries · nightly reliability and artifact depth beyond the current PR gates · full post-MVP surfaces tracked in Post-MVP Scope.
Write authority
No ambient write authority.
Direct durable memory writes, GitHub writes, shell commands, file writes, and external side effects must be policy-gated, redacted, and receipt-backed before they are considered MVP-ready. Local memory proposals remain the default unprivileged path.
Release posture
The first release line is 0.x. Each release is honest about limits
and strong enough for a credible MVP slice — but it is not a 1.0.0
stability guarantee.
Package version 0.2.0 marks the durable execution continuity
gate after the first governed agent-runtime substrate. Roadmap
milestones such as v0.12 remain implementation gates rather than
published-package compatibility guarantees.