- The default kernel is deterministic, offline, and standard-library only.
src/mind/is the source of truth. Never hand-edit generatedmind.py.python3 tools/build_single.pymust reconstructmind.pybyte-for-byte.- Plain files remain the default storage, and current plus previous formats remain readable.
- Recall stays a pure read. Durable writes are atomic, serialized, recoverable, and journaled.
Every behavior change needs an absence detector or red regression test.
Storage changes must cover:
- every durable crash point;
- concurrent writers;
- the previous format;
- below, at, and beyond each size boundary;
- backup, restore, compaction, redaction, and purge behavior.
Retrieval changes must cover:
- clean and noisy corpora;
- competing vocabulary and near duplicates;
- multilingual and temporal cases;
- empty/no-result precision;
- semantic failure and whole-ranking fallback;
- immutable LongMemEval evidence.
Every bounded constant needs a crossing test and a lifecycle policy. Every quality harness needs a green baseline preflight and a planted-defect self-test.
python3 tools/build_single.py --check
python3 tools/claims.py check
python3 tools/privacy_scan.py --tracked
python3 -m unittest discover -s tests -v
python3 bench/bench.py
python3 bench/multilang.py
python3 bench/discrim.py
python3 bench/slots.py
python3 bench/soak.py
python3 bench/fuzz.py --quick
python3 bench/autonomy.py --quickPerformance claims require immutable input, source commit, raw JSON, and a README summary generated from that JSON. Do not edit generated facts or benchmark tables manually.
Storage, privacy, semantic-process, protocol, workflow, and release changes request code-owner review. Resolve every review conversation. In a solo-maintainer repository, an administrator bypass is explicit governance debt and is not independent review.
Scoped work lives in the issues. Use a Discussion when the format, compatibility, or product boundary is still uncertain.