kijito-qa-memorylisted

# Kijito QA Memory Memory QA is creation, correction, handoff preload, and proof. Run the phases in order. A compaction handoff is not valid until Phase 4 passes twice. ## 1. Create missing memory first Enumerate every durable decision, finding, state change, user preference, failure mode, reusable command, and gate result learned since the last QA pass. For each candidate, recall before writing and create one atomic memory only when it is missing. Pass `persona="codex"` and `project="Codex"` on every write. Use honest basis, confidence, and importance. Ask both questions explicitly, and answer both before leaving this phase: 1. Existence: “What did this session learn that is not written yet?” 2. Adequacy: “Is any memory I wrote a list of the cases I happened to hit rather than the property that decides new ones?” A memory can be present, accurate, and still be a rule with an expiry date: it fails silently on the first case its author did not foresee. Restate it as the property. The existence question is the one that gets asked and the adequacy question is the one that gets skipped. Repeat until both answers are nothing. ## 2. Correct and prune Recall each topic touched: - Use `kijito_correct` for wrong or superseded claims. - Use `kijito_fade` for obsolete-but-still-true claims. - Verify operational facts against current code, configuration, or live state. - Do not treat account-wide recall as persona-private. `kijito_correct` rots every inbound `[[id]]` c