Issue2ProofTry the demo ↗

The core invention

A bug fix becomes
executable memory.

A Memory Capsule keeps the behavior, the frozen check, and the evidence needed to apply it after the original agent is gone.

issue2proof.memory.v1active
Windows device names remain rejected by safe_join.
SHA-256 · 706b7d…be7c3
2 paths1 frozen testv1

Anatomy

More than a note. More than a test.

01

Behavioral claim

The human-readable contract future changes should preserve.

02

Frozen regression

Exact executable source tied to a SHA-256 content hash.

03

Scope

Relevant paths, dependencies, and future change triggers.

04

Provenance

Source run, commit, sandbox image, and operation identifiers.

05

Boundaries

Assumptions, rejected hypotheses, limitations, and invalidation rules.

06

Recall index

Lexical terms and optional semantic embeddings for later retrieval.

Across time

The evidence outlives the session.

TodayFailure reproducedOriginal revision fails the new regression
TodayRepair verifiedRegression, existing suite, and withheld checks pass
Months laterRelated refactorA different agent touches the same behavior
Before mergeCapsule replayedPreserved, violated, or uncertain—with evidence

Precise boundary

Recall routes evidence.
Replay verifies behavior.

High retrieval relevance does not prove a regression. It decides which historical checks deserve execution. The sandbox result supplies the observed verdict.

Create and recall a capsule →