The compliant storage task stays inside the boundary.
This supporting example verifies a clean storage task against the project's JSON-only decisions. It proves the input passes; it does not claim that Mneme caused a model to choose it.
A clean input gets a clean result.
This example shows the PASS path only. The flagship demo shows a separate deny-and-retry sequence.
ADR-001 · JSON storage only. No external database on edge hardware. ADR-003 forbids an ORM in v1; ADR-005 requires extending the current storage module before rebuilding it.
-
01 Decision
The repository records JSON as an operational constraint, not an accidental implementation detail.
ADR-001 · JSON only · edge deployment -
02 Input
The bundled task extends the current JSON store and adds no database.
extend json_store.py · no ORM · no migrationBundled fixture -
03 Check
Mneme checks the task against the recorded storage decisions.
mneme check · storage_violation_count=0Current Mneme -
04 ResultPASS
The agent extends the JSON module and introduces no external persistence dependency.
Result: PASS · storage_violation_count=0
Run it yourself
Verify the compliant storage task
The product repository includes the decision corpus and clean storage prompt used by the flagship trace.
git clone https://github.com/MnemeHQ/mneme
cd mneme
pip install -e .
mneme check --memory examples/project_memory.json \
--input examples/prompt_clean.txt --query "storage backend"
# Result: PASS ยท exit 0This supporting page proves the aligned output. The flagship storage demo runs both the violating and corrected inputs.
What happened
The bundled task contains no forbidden database, ORM, or migration pattern.
It verifies a supplied task; it does not measure whether Mneme changed a model's choice.
No database service, credential path, migration history, or second source of truth is introduced.
Common questions
Why is there no DENY stage?
This page checks only the bundled clean task. It does not include a violating task to block.
What does the PASS prove?
It proves that the resulting task contains no forbidden database, ORM, or migration pattern under the recorded storage decisions.
Can the deny-to-pass sequence be reproduced?
Yes. The governed Python agent flagship runs both the violating and corrected fixtures through the same decision.
Check the decision before the refactor.
Record the storage boundary once, then use the same corpus in agent guidance and CI.
pipx install "mneme-hq>=0.9.0"