Repository navigation
feat(intent): replay bounded retained evidence with native freshness pins - #234
Conversation
814c9aa to
773b917
Compare
Move the bounded replay protocol into atomic-repository so the CLI and the daemon bind the same native pins and manifest rules. Add ReplayVaultEvidence to VaultService for context-only and replay requests; the handler gates the intent, releases the repository gate before the checker runs, and re-reads the pins afterward. The CLI sends the manifest bytes, an absolute artifact base, and the explicit checker path, then renders the same JSON shape as the local body. Plain ValidateVaultEntity stays unchanged. Evidence replay remains local-caller only and never changes acceptance status.
|
@astrogilda thank you for submitting this! I've rebased it upon the latest |
|
@graywolf336 thanks for taking it into triage, #282 and the skill read right to me. One gap: the triage summary drops the checker's details, so a reviewer can't check the allowlist the skill asks for. I opened #284 on top of #282 to carry the checker release into each decision and pin probity-verify with hashes, a CI job and Dependabot. atomicdotdev/atomic-skills#6 adds the matching skill line. |
Atomic's authoring gate checks declared verification records, but the CLI has no optional route for reviewers to replay narrowly defined claims from retained evidence. This adds
intent validate --replay-evidence MANIFEST --evidence-checker PROGRAM, plus--json --evidence-contextfor native pins. Ordinary validation remains unchanged, and replay never marks an acceptance criterion met.The manifest binds the native criterion, intent substance and full stored source, selected view and ancestor Merkle/scope chain, case, and consumer policy. Atomic explicitly invokes a locally selected checker without a shell, enforces time and input/output limits, admits JSON through its existing byte boundary, and rejects unbound responses. Pins are checked again after invocation. Supported, contradicted, and not-established results retain their scope; missing, unsupported, stale, malformed, failed, and timed-out evidence cannot pass.
An optional Python recipe uses Probity Verify's four existing bounded adapters. For example, retaining selected passages supports a source-coverage claim; changed bytes against the original digest are unknown, while a repinned record omitting a selected passage is contradicted. These claims do not establish arbitrary task correctness or authenticate a witness. Python is optional and the core dependency is unchanged.
Validation: native signed-intent CLI integration, six replay controls, five installed-checker semantic controls, retained native CLI source-coverage controls, existing vault-context/view-switch tests, and strict CLI/repository Clippy checks passed. The preceding isolated commit repairs two existing Clippy findings without changing helper behavior. The committed full CLI suite passed 2038 tests, with results retained in the delivery receipt.