Transactional plan acceptance
This page maps the original transactional product-graph plan to executable repository evidence. A row is complete only when its implementation and its named validation are both present.
| Requirement | Implementation evidence | Executable evidence |
|---|---|---|
| Ladybug is canonical and graphd is the sole writer | packages/cli/lib/graph-runtime/engine.mjs, server.mjs, client.mjs | transactional_graph_test.mjs, graphd_protocol_test.mjs |
| Generic Resources, Statements, versions, and views | graph runtime engine and query protocol | transactional_graph_test.mjs |
| Atomic typed sessions with compare-and-swap and rebase | session start, stage, validate, publish, rebase, abort | transactional_graph_test.mjs, graphd_worktree_test.mjs |
| Deterministic policy validation and Contradictions | affected-closure validation and canonical contradiction reconciliation | transactional_graph_test.mjs |
| Git branch, worktree, and multi-parent merge semantics | source-revision ancestry and branch GraphViews | graphd_worktree_test.mjs, transactional_graph_test.mjs |
| CocoIndex observations are rebuildable and never canonical | observe.mjs, observation ingress, generation tombstones | observation_cli_test.mjs, transactional_graph_test.mjs |
| Brownfield discovery reports coverage and limitations | graph observe and graph discover --brownfield | observation_cli_test.mjs |
| Every active Persona independently covers every Workflow node before implementation | coverage-bound persona_walk Resources and direct case compilation | passive_context_test.mjs, transactional_graph_test.mjs |
| WorkMap rows are mechanically derived, then resolved into an immutable requirement-to-file commitment | v4 scaffold plus modify/create and implementation/test file mappings | passive_context_test.mjs, grade_transactional_graph_evals_test.mjs |
| Every active Persona receives an independent Mission | mission compile/run and capability manifests | transactional_graph_test.mjs, eval_graph_runtime_install_test.mjs |
| Runtime evidence is normalized, isolated, and content-addressed | Mission Run/HarnessResult publication and evidence CAS | transactional_graph_test.mjs |
| Modalities and product taxonomies remain open | generic Resource kinds, predicates, and string capability requirements | transactional_graph_test.mjs |
| Stale, missing, corrupt, and capability-limited evidence fails closed | validation receipts and Mission capability checks | transactional_graph_test.mjs |
| Deterministic backup/restore is the disaster-recovery boundary | graph backup and graph restore | transactional_graph_test.mjs |
| The legacy canonical file has no live consumer or dual-write path | graph-backed skills, eval grader, and current benchmark verifier | no_legacy_runtime_test.mjs, grade_transactional_graph_evals_test.mjs, behavior_benchmark_test.mjs |
| Markdown is a version-pinned query projection only | design/verify workflow contracts | graph eval assertions and benchmark treatment gate |
| Public discovery stays compact without losing focused guidance | 10 public skills plus on-demand capability references and a complete 59-name migration map | verify_lamina_bundle.mjs, eval_install_all_skills_test.mjs |
| Every eval run loads the complete cross-referenced skill set | ASE and multi-turn install hooks copy all 10 public skills and nested references before invocation | ase_run.py, eval_install_all_skills_test.mjs |
| CLI and skills are independently installable | checksum-verified standalone CLI release assets and root GitHub skill | cli_binary_smoke_test.mjs, release_artifact_smoke_test.mjs, eval_graph_runtime_install_test.mjs |
| Current evals exercise graph state rather than legacy artifacts | live graph assertions in evals/hooks/grade-lamina.mjs | generated-suite validation and graph grader tests |
| Current Lamina benchmark cells install and enforce the graph runtime | standalone CLI release contract, graph backups, fail-closed treatment gate | validate-transactional-pilot.mjs, behavior_benchmark_test.mjs |
Intentionally deferred v1 work remains outside the accepted plan: cross-clone graph synchronization, distributed consensus, arbitrary project-supplied validators, raw Cypher access, multiple graph backends, and semantic-search infrastructure.
The architectural rationale is recorded in ADR-001 and the current distribution decision in ADR-013 . The current Persona/WorkMap simplification is recorded in ADR-011 .
Last updated on