Current State

Implemented in v0

  • Private, single-user browser test bed.
  • Manual capture using IDE#, QUE#, and DEC#.
  • Optional PRJ:name routing metadata.
  • Role-specific identifiers such as IDE-0001 and QUE-0001.
  • Preserved original source, separately stored AI Snapshots, and Question Results.
  • Open-to-answered Question lifecycle.
  • Duplicate-delivery protection when a stable delivery identifier is provided.
  • Search and Card Summary / Card Detail views.
  • EvenFlow Lean, Regular, and Review layouts composed from shared visibility controls. Layout and fine-grained display preferences remain on the device and never remove stored Card data.
  • Device-local capture draft preservation across refreshes and layout changes, cleared only after a confirmed capture.
  • Relational Project associations and a first category taxonomy, while retaining the legacy Project field for adapter compatibility.
  • Composable All Cards, Intake, Open Questions, and Decisions Views over the same Card collection.
  • Deployed schema migration runner through version 2.
  • Exact preservation for new Source Records with deployed database update/delete guards. Earlier captures remain exactly as the v1 adapter stored them; previously trimmed whitespace cannot be reconstructed.
  • Deployed Unicode code-point offset contract shared by Python and PHP adapters.
  • Deployed source identity, revision, idempotency-collision, and bridge-consent contract scaffolding.
  • Checksummed export/restore with identity-preserving round-trip tests, including a production-copy rehearsal.
  • Deployed proposal staging table excluded from authoritative Card payloads.
  • Verified pre-v2 production backup retained after successful live migration.

Proposed, not implemented

  • Automatic inline capture from Chat, Gemini, and other AI platforms.
  • MCP or equivalent cross-platform capture bridge.
  • Individual user identity, roles, permissions, and separate Ledgers.
  • Mature Card-to-Card dependencies and additional taxonomy vocabularies.
  • Versioned development history beyond Snapshots and Results.
  • In-product feedback review and documentation promotion workflow.
  • User-facing proposal acceptance and rejection workflow.

Explicit v0 boundary

The live deployment uses one private access key. It must not be distributed as a multi-user authentication system. Early human testing should be facilitated until individual accounts, attribution, revocation, and privacy boundaries exist.