ProofGit
Summary · exact lines · path · commit SHA · trust status
Two products · separate authorities
Know what the code does.
Remember why it does it.
ProofGit supplies current, source-cited repository evidence. ProofMEM preserves the approved decisions and constraints that should survive the session. Caveau Harness assembles both for planning and implementation without collapsing one authority into the other.
ProofGit is available now. ProofMEM founding access is open and free, with no card required; our team reviews every application. They keep separate credentials, subscriptions, and authority boundaries.
Using both? The ProofGit + ProofMEM pairing offer gives ProofMEM founding members a ProofGit discount, priority ProofMEM review for ProofGit customers, and a free guided Caveau Harness setup session. Details on proofgit.com and proofmem.com.
REVIEW DOCKET
task / evidenceProofMEM
Objectives · constraints · decisions · accepted lessons
Task assembly
A question moves through six visible hand-offs.
Repository content remains quoted evidence. Approved memory remains governed context. A person reviews the proposed work before anything becomes a durable lesson.
- 01
Ask
Name the architecture, behavior, bug, review, or change question.
- 02
Recall
ProofMEM returns approved context for the active scope.
- 03
Prove
ProofGit returns current explanations and exact source evidence.
- 04
Separate
Caveau Harness labels repository evidence distinctly in PLAN and WRITE.
- 05
Review
A person checks intent, source, tests, and the resulting work.
- 06
Accept
Memory may retain the decision and a bounded evidence pointer—not copied code.
Alone and together
Use only the authority the work needs.
Both products are useful alone. Bring them together when a task genuinely depends on current implementation and approved, cross-session intent.
“What does this repository do now?”
For architecture discovery, source-cited answers, code review, repository health, and agent grounding.
Explore ProofGit“What have we approved and learned?”
For scoped continuity, durable decisions, organizational lessons, and governed agent recall.
Explore ProofMEM“What does the code do—and why did we choose it?”
For planning and implementation that must respect approved constraints while remaining traceable to the code that exists now.
Sanitized pilot record
Trivia & Tunes: ten tasks, all acceptance checks met.
The internal pilot covered architecture discovery, behavior explanation, bug location, change planning, code review, and cross-session continuation.
- Task set
- 10 / 10 accepted
- Repository scope
- One allowlisted repository
- Evidence state
- Current + verified only
- Durable source text
- None persisted
- Disclosure boundary
- No private code, prompts, repository identifiers, tokens, customer data, or unsupported performance numbers.
Authority boundaries
Not a new bundle. Not one system of truth.
This is a controlled context-assembly workflow across two standalone products—not a promise of shared identity, included entitlement, or automatic judgment.
No automatic memory writes
Evidence becomes durable context only after explicit human acceptance.
No copied source bundles
ProofMEM may retain a bounded pointer, never source lines or full evidence results.
No shared login or included entitlement
ProofGit and ProofMEM keep separate credentials and subscriptions.
No automatic drift detection
The workflow can expose disagreement; it does not claim to monitor or resolve it automatically.
No “single source of truth”
Repository state and approved organizational context remain deliberately different authorities.
Code remains untrusted input
Quoted repository content informs the task; it cannot override policy, constraints, or review.
Start with current code
Prove what. Then preserve why.
Begin with a card-backed 14-day ProofGit trial. Add ProofMEM when approved context must survive beyond one task or session.