KCAE.MEMORY:4 - Solution

KCAE.MEMORY:4.1 - Retain the smallest revisable episode

Preserve the original expression or observation that matters, the receiving use, allowed source return, current interpretation, rejected interpretations that could otherwise recur, unresolved questions and the grounds of any conclusion. Keep source text separate from the system’s interpretation. An early cue may have no selected method, no confirmed anomaly and no confidence score. That is a legitimate unresolved result.

Obtain the retention purpose, scope, access and expiry from the owner. Avoid copying private source material when a protected reference suffices; test that the reference will remain obtainable by an authorized later reader. If the content must be erased, retaining an embedding or paraphrase may still retain the prohibited information. Apply the deletion meaning to every derived copy.

For CedarBench, retain “senior analyst removes duplicates after on-time exports,” the customer proposal, the missing protocol question and the reason a speed-only interpretation was insufficient. Do not reduce the record to “resend recommended.” It may be reopened after a protocol change, even if the original customer never used the word reconciliation.

KCAE.MEMORY:4.2 - Store conditional connections with their dependencies

A reusable connection says which contribution helped which kind of receiving result, under what source edition, case conditions, criterion and support. Retain the source address and relevant dependency slice. Store an assessment or recommendation as that result, not as a timeless fact about the source. An observed successful application additionally needs its actual conditions and outcome; a proposed sequence has no observed success merely because it was stored.

Key reuse on the conditions that can change the answer, not only a semantic similarity score. A prior answer can be used directly when its dependencies and receiving use still hold. Where only part survives, reuse that part and reassess the changed premise. Missing dependency information makes the old answer a candidate to inspect, not a qualified shortcut.

Repeated requests can justify a response cache, a source-to-question map or a reusable aid. Choose the smallest representation that serves the repetition. A source-based cached explanation and a trained retrieval model have different refresh and deletion costs. Do not train a broad model merely to avoid a small explicit dependency check.

KCAE.MEMORY:4.3 - Let new material find relevant old questions

Maintain a bounded collection of authorized open questions and conditional uses. When a source changes or a newly inspected method supplies a different contribution, query that collection by its possible receiving results and conditions. Reassess candidate episodes against their original cues; do not simply append the new method to every similarly tagged case.

This reverse lookup can be indexed lexically and semantically, with the same source-return and blind-spot limits as forward retrieval. Preserve a route to open episodes outside the existing category. A periodic sample or targeted direct inspection can reveal cases the category map hides. Selection for such inspection must have a declared scope and cost; it is not proof that every past episode has been reconsidered.

Publish a changed connection only after the relevant source and current case basis are inspected. The old configuration may no longer be observable, or the user’s need may have ended. Return “potentially relevant, present situation unknown” rather than an unsolicited action based on an old conversation. Permission to remember is not automatically permission to interrupt; KCAE.ENCOUNTER governs the latter.

KCAE.MEMORY:4.4 - Improve recognition questions from consequential misses

Take actual misses and false matches whose remedy can change use. Compare them with matched cases and nearby non-fits. Ask what observable question would have distinguished them before the result was known. “Does success require repeated manual compensation?” may expose a broader family than “Did the export fail?” The wording and its observable inputs matter more than a new tag name.

Derive candidate questions from the episodes and subject knowledge, then test them on withheld or independently constructed cases, including negatives and unknowns. A generated question tested only on the examples that generated it supplies no independent recognition evidence. Reject a question that cannot be answered from the authorized event projection, or obtain the needed observation through an approved route.

Keep the question as a useful aid, not an exclusive admission gate for every future concern. Provide an open route for an unrecognized cue. If features become a learned classifier, preserve the training basis, model version, evaluation population and refresh conditions. KCAE.EVAL compares its gain with direct source-based inquiry and the prior recognition aid.

KCAE.MEMORY:4.5 - Expire, invalidate and learn without rewriting the past

Use dependency changes from KCAE.CHANGE to reopen stored connections. Distinguish changed source content, changed case facts, changed authority, changed model and an expired receiving opportunity. A newer rule can invalidate current advice without falsifying the earlier historical record. Correct a past factual error with its grounds; do not silently relabel the original observation to match the new interpretation.

Periodically inspect whether retained material is still permitted and useful. Remove obsolete prompts and expired copies. Preserve only the evidence needed for any legitimate historical or accountability use. Measure the effort saved by reuse against maintenance, false suggestions and exposure. Memory that produces more unhelpful work than it saves should be narrowed or removed.