CORTEX: MEMORY THAT KEEPS CONTEXT AND PURPOSE TOGETHER Work architected at Fifth9 Memory architecture and implementation work — The explanatory layers group responsibilities. They do not claim that every proposed memory tier or learning loop is operational. Cortex separates capturing information, preserving its context, retrieving relevant records and caring for the resulting memory. Memory retrieval provides evidence to a task; it is a different mechanism from changing the parameters of a neural model. What should an AI collaborator remember when the work continues? Help a continuing collaboration recover what matters, where it came from and why it was retained. Useful memory is more than storage. A retained statement needs enough context to answer who it concerns, where it came from and whether it still applies. Retrieval should help a collaborator inspect relevant evidence, not promote any remembered sentence into unquestionable fact. BUILDING BLOCKS Capture and scope Record relevant information with its intended scope. Receives: Conversation, work events and operator contributions. Produces: Scoped records with their origin and purpose. Working and persistent memory Support immediate context and records that outlast a session. Receives: Records with different uses and lifetimes. Produces: Working context and retained material for later retrieval. Provenance and lineage Keep the origin and development of information inspectable. Receives: Source references, revisions and relationships. Produces: A record of where information came from and how it changed. Retrieval Find material relevant to the current question. Receives: A question, context and access scope. Produces: Candidate evidence with enough context to interpret it. Memory care Manage correction, retention and removal over time. Receives: Corrections, retention choices and memory-quality observations. Produces: Updated records and a deliberate memory lifecycle. WALKTHROUGH 1. Capture with context Retain a contribution with its purpose, origin and enough context to understand what it refers to. A useful memory should remain distinguishable from a model-generated guess or an observation about a different situation. 2. Place it appropriately Distinguish the context needed for an immediate task from records intended to remain useful later. The explanatory layers describe different lifetimes and responsibilities, not a promise that every proposed memory tier is operational. 3. Retrieve for a task Ask what information this task needs and retrieve within the relevant scope. A semantically similar record can still be outdated, incomplete or inappropriate for the current question. 4. Use and examine Interpret the evidence and check whether it actually helps answer the question. The person or reviewing process still needs to judge whether the context supports the recommendation; retrieval quality and answer quality are separate questions. 5. Correct and maintain Reconsider mistaken or obsolete context and decide what should remain available. Retention, correction and forgetting need an account of derived records as well as original material, and their effects should be examined explicitly. ILLUSTRATIVE EXAMPLE — Return to an earlier design decision A team returns to a design decision after several weeks. The collaborator retrieves the earlier requirement, decision and reason for rejecting an alternative. The person can correct an outdated assumption before the next recommendation is made. If an older decision conflicts with a newer constraint, the person needs to see that conflict and correct the context before relying on the next recommendation. Relevant earlier context that the person can inspect and correct. Illustrates useful continuity, not a guarantee of recall accuracy or an already-proven outcome-learning loop. Why these responsibilities are separate Memory care and learning have different jobs. Correcting a record, changing retention or improving retrieval does not necessarily change a model’s learned capabilities. The architecture makes room for those processes while leaving each improvement claim to an appropriate evaluation. SCOPE Persistent memory records, scoped retrieval and provenance-oriented archive work. Benchmark and memory-care work that examines retrieval and retention behaviour. REMAINING QUESTIONS Does retrieved context improve the person’s task? Which records deserve continued retention? Can an outcome improve future recall without amplifying mistaken information? BOUNDARIES AND EVALUATION Retrieval versus answers: Retrieving relevant evidence does not guarantee a correct final answer. Evaluation: Assess retrieval separately from the final answer and inspect the supporting records. Scope and retention: Retention must preserve scope and permit correction or forgetting. Evaluation: Test relevant scope boundaries, corrections and the effects of retention choices. Measured improvement: Recorded outcomes do not prove that memory quality improves because of them. Evaluation: Compare an explicit memory change against an appropriate baseline instead of inferring improvement from new records. The aim is continuity that reduces repetition and preserves useful experience while keeping people in control of what is retained and trusted. AI Initiative — public architecture guide.