REFEvidence & memory
Require evidence
A result should be inspectable after the session ends.
This documentation describes the Antecant operating model. The website demonstrates it locally; it does not connect to an autonomous runtime.
Attach the artifact
Evidence can be a test output, reviewed diff, source excerpt, measurement or deployment receipt. Record its origin, related invocation, source revision and the acceptance condition it addresses.
Check relevance and freshness
A passing test from a different revision does not prove the current release. A source can be authentic and still irrelevant to the claim. Acceptance needs both valid provenance and a meaningful relationship to the desired outcome.
Record disagreement
Keep failed checks, dissenting reviews and uncertainty alongside successful results. An institutional record that contains only favorable evidence is a marketing artifact, not a reliable decision history.
Promote learning carefully
Memory should retain reusable decisions and methods with their evidence and invalidation conditions. Avoid promoting an unverified agent summary into authoritative organizational knowledge.