Objectives · constraints · decisions · lessons
ProofMEM + ProofGit · separate authorities
Know what the code does.
Remember why it does it.
ProofMEM preserves approved intent across sessions. ProofGit supplies current repository explanations and exact supporting source. Caveau Harness assembles both for planning and implementation—without copying the repository into memory.
ProofGit is available now. ProofMEM is invite-only and currently free during its beta. Accounts, credentials, and subscriptions remain separate.
TASK CONTEXT
scope / reviewedSummary · path · exact lines · commit SHA
Task assembly
From a question to a reviewed, evidence-backed change.
Memory informs the task. Repository evidence supports the technical answer. Neither is allowed to silently become an instruction.
- 01Ask
Name the architecture, behavior, bug, review, or change question.
- 02Recall
ProofMEM retrieves approved context for the active scope.
- 03Prove
ProofGit retrieves current explanations and exact source evidence.
- 04Separate
Caveau Harness labels repository evidence distinctly in PLAN and WRITE.
- 05Review
A person checks intent, source, tests, and the proposed work.
- 06Accept
Memory may retain the decision and a bounded evidence pointer—not copied code.
Alone and together
Not every task needs both.
Add the second authority when it genuinely changes the quality of the decision—not simply because another integration is available.
Retain approved context.
Best for cross-session continuity, scoped decisions, organizational lessons, and governed agent recall.
Explain the current repository.
Best for architecture discovery, source-cited answers, code review, repository health, and agent grounding.
Compare approved intent with current implementation.
Use both when a plan or change must respect durable constraints and remain 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. Every query remained inside one allowlisted repository and admitted only current, verified evidence.
- 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
No silent promotion from evidence to memory.
The connection is a controlled context assembly path, not a claim that two products have become one database, account, or subscription.
No automatic memory writes
Evidence does not become a durable decision until a person explicitly accepts it.
No copied source bundles
ProofMEM stores approved context and bounded evidence pointers, not source lines or full result sets.
No shared login or included entitlement
ProofGit and ProofMEM remain standalone products with separate credentials and subscriptions.
No automatic drift detection
The workflow can reveal a disagreement; it does not claim to monitor or resolve it automatically.
No “single source of truth”
Approved intent and repository state are deliberately separate authorities with different owners.
Code remains untrusted input
Repository content is quoted evidence, never an instruction that can override policy or human review.
Start with the repository
Prove what.
Then preserve why.
Start a card-backed 14-day ProofGit trial. Add ProofMEM when approved context must survive beyond one task or session.