Keep intent and actions together
A run identifies the task. Its event ledger records actions and results, while Git capture binds the base, head and tracked-file diff to a patchset.
AI-assisted development / Provenance
Keep the story behind every code change.
A code diff shows what changed. ChangePlane connects it to the intent, recorded actions, checks and decisions that produced it. The result is a local record you can inspect, seal and carry into a replay.
From an agent session to a reviewable record
Imagine an agent adding retry logic. A useful review needs the patch, the reason for it and the checks that followed. ChangePlane keeps those pieces connected.
A run identifies the task. Its event ledger records actions and results, while Git capture binds the base, head and tracked-file diff to a patchset.
Evaluation combines scored dimensions with hard gates. A seal binds hashes of the recorded artifacts, including optional protocol and harness-invocation records.
A replay bundle carries the captured patch and supporting record. Replay applies the patch in a fresh worktree by default and produces its own verification report.
Interactive illustration · fictional data
This small browser demonstration hashes three fictional artifacts. Choose a change made after sealing and compare the current record with the original fingerprints.
Each case starts from the same original seal.
Add a bounded retry to the fetcher.
Three checks passed, including the timeout case.
retry_limit = 2
Integrity result
The original seal is prepared when this page loads.
A matching fingerprint means the selected artifact matches what was sealed. Review still determines whether the original work was correct.
This illustration runs entirely in your browser with synthetic data. The Python implementation seals a richer record. Version 1 uses unkeyed SHA-256: someone able to rewrite both the artifacts and their seal can recompute the hashes.
Inside the project
Python’s standard library and SQLite provide the core. Git remains responsible for commits, branches and worktrees. ChangePlane adds typed records of the surrounding development work.
5PP phases, DIALECTIC exchanges and DIAL-4 claims can become part of a run’s protocol trace. DIAL-4P produces views such as a developer handoff or seal report from that record.
The harness registry describes capabilities. Invocation records capture their use in a run. The capability router recommends tools and workflows; the operator and execution tools perform the work.
The command-line interface and stdio MCP server expose run creation, event recording, capture, evaluation, sealing, inspection and replay bundles. The autopilot surface currently plans bounded experiments in dry-run mode.
changeplane init changeplane start --intent "add a bounded retry" changeplane event --type note --summary "reviewed the timeout path" changeplane git capture changeplane seal --decision APPROVE changeplane seal verify changeplane inspect
The decision supplied to sealing is an explicit recorded decision. It is not an automatic approval or a Git merge.
Implementation check / 12 November 2026
The actual sealing and verification functions were exercised against temporary synthetic records at source revision 32cb7840915d. The expected outcome was observed in all four cases.
| Case | Expected verification | Observed |
|---|---|---|
| Original record | Matches the seal | PASS |
| Event edited after sealing | Event-log mismatch | PASS |
| Intent edited after sealing | Run-metadata mismatch | PASS |
| Patch edited after sealing | Patch-content mismatch | PASS |
These are focused integrity checks. The browser demonstration is a separate, simplified explanation.
Related work