Evidence ledger
JSON cases connect the review, commits, rule, and replay result. No hidden model memory.
v0.10 beta · local repository learning
Keep the correction. Prove the check.
Preserve a reviewed regression test. Prove it fails on the broken code and passes on the fix. Check later changes under constrained local execution.
A failure becomes repository memory
One review. One replay. One rule your tools can check.
Follow the complete v0.10 beta workflow. This preview is illustrative; the published npm beta includes a seeded literal case you can run without an account, model key, or Docker.
Run the one-command quickstart →Illustrative previewv0.10 beta workflow
spine learn --case failure.json
case tenant-query imported
- source
- manual review evidence
- failure
- invoice query omitted its tenant filter
- scope
- src/invoices.js
The preview uses a seeded example. Spine stores local evidence and checks literal rules; it does not claim to infer every architectural mistake.
The learning loop
Evidence in. Verified guardrail out.
Spine makes each step reviewable. The beta stays deliberately narrow so a passing replay means something concrete.
- 01
Capture
Import a manual case file or GitHub review metadata. Evidence stays explicit and inspectable.
- 02
Propose
Create a scoped require-text or forbid-text rule with a file glob and source trail.
- 03
Replay
Read historical Git objects to prove the broken commit fails and the corrected commit passes.
- 04
Enforce
Run verified rules against a diff in CI, then serve only relevant context to any MCP client.
What replay proves
The rule matches the history you gave it.
A verified rule failed on the recorded broken commit and passed on the recorded correction. That is strong evidence for a narrow check. It is not a promise that every future defect is prevented.
$ spine replay tenant-query
✓ broken demo commit required literal missing
✓ corrected demo commit required literal present
verified: require "WHERE tenant_id = ?"
scope: src/invoices.js
source: manual review evidenceExecutable correction pilot
Keep the test that proved the fix.
The source-available correction pilot captures a user-reviewed Node built-in test from an explicit fixed commit. Verification pairs those same test bytes with each revision’s own source files and runs both in constrained Docker containers.
A correction stays a candidate until the broken revision fails, the fixed revision passes, and the execution controls succeed. The first pilot is intentionally narrow: dependency-free JavaScript using node:test.
Why not just write a test?
Write the test. Keep its evidence.
Spine does not replace your normal test suite. It keeps the reviewed test, source-file scope, broken/fixed proof, and execution policy together. Reports fingerprint each tested snapshot; current-tree checks rerun the correction under the same controls.
Context can surface an unverified correction as a candidate, but only a successful controlled run is labelled verified.
Read the correction model → Propose a pilot case →The v0.10 beta surface
Small primitives that compose into a useful control loop.
Compile and drift workflows remain available. Learning, replay, guard, context, reports, CI, and MCP form the new center of gravity.
Literal guardrails
Deterministic forbid-text and require-text checks scoped by repository globs.
Git replay
Read-only historical verification. Spine inspects commits; it does not rerun an AI agent.
CI guard
Machine-readable output and diff-aware checks make verified rules useful on every pull request.
Relevant context
Ask for files and receive applicable rules through the CLI or local MCP server.
Local reports
Generate an HTML report that a maintainer can review, archive, or share with a team.
Need to test an actual configured agent or evaluator? spine evaluate is a separate, explicit execution path with different risks and costs. Read the evaluation contract →
Try the literal loop first
One command. A complete broken-to-fixed proof.
The command downloads the exact published npm beta, then runs the Docker-free literal demo. It needs Node 22.12+ and Git, and uses the network only to install the package. No account or model key required.
run the verified npm beta
$ npx --yes --package=project-spine@0.10.0-beta.3 spine demo§ KEEP THE CORRECTION
Your code review found it.
Your repo should remember it.
Local, deterministic, MIT licensed, and built for maintainers who work with more than one coding agent.