Specifications and Architectural Guidance for Multi-Agent Transactive Memory (MATM) in LLMWikis.org

Full report

On this page

1. Executive Summary and Strategic Orientation

The accelerated deployment of heterogeneous Large Language Model (LLM) agents across open and interactive environments has precipitated a fundamental paradigm shift in artificial intelligence architecture. As base-model reasoning capabilities have demonstrated diminishing marginal returns on raw parametric scaling, the primary bottleneck in self-evolving agent ecosystems has transitioned from isolated task execution to the curation, governance, and population-level sharing of procedural knowledge1. In response to this shift, the integration of Multi-Agent Transactive Memory (MATM) into the LLMWikis.org governance framework establishes a specialized, highly structured architectural standard designed to support scalable experience reuse across decentralized agent populations3. Historically, multi-agent frameworks permitted execution agents to write their internal states, procedural discoveries, and environmental observations directly to shared memory repositories, treating vector databases as uncurated logs rather than governed knowledge graphs. This architectural anti-pattern inevitably results in exponential memory pollution characterized by stale facts, unrectified contradictions, cross-scope contextual leakage, and severe privacy violations1. The MATM framework, adapted from foundational organizational psychology, resolves this crisis by establishing a strict bifurcation of cognitive labor: the task of executing workflows is entirely decoupled from the task of governing memory6. Through the deployment of a dedicated Memory Curator Agent and the enforcement of explicit epistemic firewalls, MATM ensures that durable memory is earned through rigorous validation rather than granted by default6. This document provides exhaustive, expert-level specifications for integrating MATM principles into LLMWikis.org. It outlines the theoretical and mathematical foundations of memory hallucination, codifies the nine-kind memory taxonomy and five-operation write primitives, defines the four-scope organizational partition, and establishes the strict handbook authority required to construct compliant, agent-safe wiki templates. Furthermore, it provides direct guidance for contributors seeking to expand the LLMWikis.org knowledge base, detailing the strategic deployment boundary maps, reader-action orientations, and metadata compliance protocols required to maintain the integrity of the broader Teleodynamic ecosystem8.

2. The Theoretical Evolution: From RAG to Transactive Memory Systems

To effectively implement and govern Multi-Agent Transactive Memory within an LLM wiki, contributors must understand its theoretical antecedents and its divergence from traditional information retrieval methodologies.

2.1 The Foundations of Transactive Memory in Organizational Psychology

The concept of transactive memory was originally articulated by social psychologist Daniel Wegner in the mid-1980s as a sophisticated alternative to outdated and scientifically ambiguous "group mind" theories11. Wegner observed that human groups optimize their cognitive load by distributing the responsibility for encoding, storing, and retrieving information across networks of individuals based on specialized expertise11. In a Transactive Memory System (TMS), participants do not attempt to memorize the entirety of a shared experience; rather, they memorize the location of the expertise, allowing the group to function as a highly efficient, integrated information processor11. A robust TMS relies on three interrelated behavioral indicators and cognitive processes. The first is directory updating, a continuous knowledge inventory process whereby individuals learn "who knows what" by observing peers' specific domains of competence12. The second is information allocation, occurring during the encoding phase, where incoming data is tagged with responsibility labels and routed to the designated expert rather than being broadcast to the entire group11. The third is retrieval coordination, wherein the group utilizes its shared "directory of directories" to query the appropriate specialist, drastically reducing the search space and enhancing decision-making efficiency12.

2.2 Transposing Human Cognition to Agentic Infrastructure

The transition from human organizational psychology to artificial agent populations addresses a critical infrastructural void. Traditional Retrieval-Augmented Generation (RAG) systems operate primarily by fetching human-authored documents from external corpora to support a single agent's generation process3. MATM extends this paradigm significantly by functioning as a specialized retrieval system over agent-generated artifacts3. In interactive environments such as WebArena and ALFWorld, agents produce long, highly structured interaction trajectories that encode valuable procedural knowledge3. Under standard frameworks, these artifacts are typically discarded after a single use or retained only by the producing agent, forcing newly instantiated agents to repeatedly rediscover existing solutions in isolation2. MATM transforms this dynamic into a two-sided marketplace for procedural knowledge, where producer agents contribute interaction trajectories to a shared repository, and consumer agents retrieve them to improve downstream task performance and step efficiency without requiring centralized coordination or joint training2.

2.3 The Failure Modes of Direct-Write Memory Architectures

Between 2023 and 2025, a sequence of research contributions established that LLM agents could materially improve at recurring tasks by retaining workflow artifacts, as demonstrated by systems like Voyager for skill libraries, Reflexion for verbal self-criticism, and Agent Workflow Memory1. However, as these systems scaled into production frameworks with multiple heterogeneous agents, a systemic failure mode emerged. When execution agents are permitted to write durable memory directly, the shared memory store rapidly degrades into an unmanageable state. A worker agent inherently biases toward retaining everything it produces, lacking the objective distance required to govern knowledge6. This produces a strictly monotonic memory store that accumulates stale facts where outdated project structures continue to be retrieved as current truth1. It creates unrectified contradictions, where Agent A asserts a preference and Agent B later revises it, resulting in both versions persisting with equal weight and causing retrieval schizophrenia1. Furthermore, it induces cross-scope leakage, where a specific procedure meant for a single project is universally applied, and triggers privacy violations when localized session context is broadcast to a global pool1. The underlying issue is that executing a task and governing a memory store are fundamentally different cognitive processes; conflating them within a single agent guarantees systemic pollution6.

3. The Mathematical Bounds of Multi-Agent Memory Degradation

The necessity of implementing a governance layer within LLMWikis.org is not derived solely from qualitative observation; it is formally proven through mathematical bounds detailing the compounding nature of agentic hallucination in uncurated systems1. To establish accurate guidance for MATM deployments, wiki architects must incorporate these mathematical realities into their structural planning.

3.1 The Uncurated Growth Baseline

In a baseline uncurated system, we observe a self-evolving agent population over discrete time steps. Worker agents emit a Poisson-distributed number of candidate memory events at a rate. Assuming an intrinsic per-event hallucination or error probability, every emitted event is written directly to the durable memory state1. In this regime, the expected number of hallucinated entries grows linearly with time. Under standard retrieval mechanisms that surface a logarithmic number of entries per query based on memory size, the probability that a retrieved context window contains at least one hallucinated or contradictory entry is a slowly growing, but strictly monotonic, failure rate. Over long horizons, this probability approaches absolute certainty1. Monte Carlo simulations conducted over extended time horizons demonstrate that uncurated multi-agent systems saturate at near-certain hallucination rapidly, reaching a 94 percent failure probability by day 30 and a 99 percent failure probability within a single year1. This phenomenon occurs because retrieval coverage expands logarithmically, while the polluted memory pool expands linearly, guaranteeing that agents will eventually base their actions on false or superseded premises1.

3.2 The Curator-Bounded Hallucination Theorem

To counteract this exponential degradation, the MATM architecture introduces an admission control layer characterized by two specific variables: an admission rate, representing the proportion of candidate events allowed into durable storage, and a filter accuracy, representing the mechanism's ability to successfully identify and discard erroneous or unverified events1. The formalization of this relationship, defined as Theorem 1 in foundational MATM research, proves that the per-retrieval hallucination probability in a curated regime can be strictly bounded1. The asymptotic corollary to this theorem demonstrates a profound structural reality: in the long-horizon limit, any positive filter accuracy yields unboundedly better long-term reliability compared to the uncurated baseline1. Crucially, the mathematical proof reveals that the admission rate acts merely as a multiplicative slowdown in the base of the equation, whereas the filter accuracy enters the exponent. This signifies that the protective effects of accurate memory filtering compound logarithmically over time, whereas simply writing less information does not fundamentally alter the trajectory of degradation1.

3.3 Operating Regimes and LLM Capabilities

When configuring MATM thresholds within LLMWikis.org templates, architects must target realistic operating regimes. Achieving a theoretical filter accuracy of 95 percent on complex classification tasks pushes the boundaries of current LLM reasoning capabilities, often resulting in severe computational and latency overhead1. Exhaustive simulation data indicates that a practical regime—targeting an admission rate of approximately 30 percent and a filter accuracy of 90 percent—achieves the optimal cost-to-quality ratio1. Operating within this envelope, the system writes only 27 percent as much memory as an uncurated baseline while delivering a massive 3.2-fold reduction in long-term hallucination rates. Consequently, LLMWikis.org guidance recommends this specific configuration envelope as the default standard for all enterprise MATM deployments1.

4. The Architectural Solution: The Memory Curator Agent

To instantiate the mathematical bounds required for stable transactive memory, LLMWikis.org specifies the deployment of a dedicated Memory Curator Agent. This specialist acts as the sovereign governance layer, operating as an epistemic firewall between the execution environments and the durable storage infrastructure1.

4.1 The Decoupling of Generation and Admission

Under the LLMWikis.org MATM architecture, worker agents are strictly prohibited from writing to any durable memory store. Instead, they are restricted to emitting structured candidate events known as Memory Tickets1. These tickets encapsulate the proposed memory content, a suggested organizational scope, a reference to supporting evidence, and an internal confidence score indicating the worker's certainty regarding the observation1. The Memory Curator Agent assumes exclusive ownership over all durable writes. It serves as an active deduplication, redaction, and conflict resolution engine1. By maintaining an aggregate view of the total ticket flow from heterogeneous sources, the curator can detect epistemological collisions. If a finance agent emits an unverified hypothesis regarding a project timeline, and an engineering agent subsequently reads it as fact, the entire system's world model fractures1. The curator prevents this by synthesizing contradictory inputs into nuanced, unified records, ensuring that retrieval processes surface cohesive transactive memory rather than a chaotic log of competing claims7.

4.2 Managing the Curator Scaling Trap

While the Memory Curator pattern resolves the problem of memory pollution, it introduces a potential architectural vulnerability known as the scaling trap. As a multi-agent population scales to dozens or hundreds of concurrent workers, funneling every emitted Memory Ticket through a full-inference LLM curator creates a severe latency bottleneck, effectively moving the system's operational constraint from capability to admission bandwidth7. To mitigate this, LLMWikis.org deployment standards mandate a hybrid routing architecture. For high-volume environments, the primary admission and routing rules must be executed by a highly efficient, declarative classifier—a small, specialized model that maps the event taxonomy and proposed scope to a routing decision at low latency7. The computationally expensive, full-parameter LLM curator is invoked exclusively for ambiguous edge cases, complex conflict resolutions, and the synthesis of superseding decisions. This dual-tiered approach ensures that directory updates remain fluid and non-blocking while preserving the high filter accuracy required by Theorem 17.

5. Scope Partitioning and the Organizational Memory Matrix

A central tenet of human Transactive Memory Systems is that knowledge belongs to specific, contextually bounded interaction spheres13. LLMWikis.org translates this principle into computational architecture by mandating a strict scope partitioning model. The Memory Curator Agent utilizes a four-scope partition—often extended to a five-layer operational contract in production implementations—to prevent cross-scope leakage and maintain localized relevance1.

5.1 The Five-Layer Operational Contract

The integration of MATM into LLMWikis.org requires wikis to explicitly declare their namespace boundaries according to the following scopes:

By forcing all incoming Memory Tickets through this partition logic, the Curator enforces a conservative default posture. If an event contains unsupported claims, introduces ambiguity, or possesses temporary utility, the Curator explicitly overrides the worker's suggested scope and downgrades the ticket to Session memory or executes a terminal discard7. Within this framework, durable memory is treated as a highly privileged state that must be rigorously earned7.

5.2 Promotion Paths and Temporal Decay

An advanced feature of the LLMWikis.org scope partition is the management of temporal decay and the promotion path from Session scratch6. Because highly valuable context often begins as throwaway observations, the Curator monitors Session scopes across multiple timelines. If an observation recurs with high frequency across independent sessions, the Curator can escalate the entry to a durable Project or Team scope, transforming localized intuition into systemic procedural knowledge6. Conversely, to combat the accumulation of obsolete context, the system requires temporal decay mechanisms, such as last-accessed timestamps, enabling slow-loop garbage collection of facts that were valid at encoding but have since grown stale6.

6. The MATM Ontological Framework: Taxonomy and Write Primitives

For LLMWikis.org to maintain a cohesive, machine-readable directory, the data structures handling memory handoffs must conform to rigid semantic schemas10. When updating wiki guidance for MATM, contributors must document and enforce the Nine-Kind Memory Taxonomy and the Five-Operation Write Primitives1.

6.1 The Nine-Kind Memory Taxonomy

Worker agents are required to semantically classify their memory emissions. The LLMWikis.org JSON event schema mandates the use of a strict nine-element taxonomy to categorize the epistemological weight, actionability, and evidentiary requirements of the information1.

6.2 The Five-Operation Write Primitives

When the Memory Curator Agent acts upon a validated memory ticket, it must execute one of five terminal disposition actions. This formalized write model prevents the monotonic accumulation of unstructured logs and forces the memory store to behave as a curated knowledge graph1. The system executes an Append operation exclusively for entirely new, non-redundant entries that successfully pass all validity, redaction, and scope checks, adding novel nodes to the transactive memory directory1. The Update primitive is utilized only when an existing memory entry is demonstrably superseded by new evidence; the previous entry is modified, but a lineage trace is strictly maintained to understand the evolution of the state, ensuring that downstream agents are not operating on fractured timelines1. When a procedure or fact is no longer valid but must remain in the ledger for historical audit trails—or to act as a negative constraint preventing agents from retrying known-failed paths—the system executes a Deprecate operation, heavily penalizing the entry in future retrieval rankings1. If the Curator detects that an incoming ticket contradicts an existing durable memory and lacks sufficient evidence to override it, a Conflict operation is logged. This flags the competing entries, alerting human reviewers or halting automated workflows to maintain epistemic safety1. Finally, the Discard operation acts as the terminal disposition for low-confidence, highly ambiguous, unsafe, or redundant events. Discarded tickets never enter the durable storage layer, acting as the primary defense mechanism against vector store pollution1.

7. The Nine-Step Curation and Admission Pipeline

The transition of a memory event from a worker's localized context window to a durable, retrieved artifact within LLMWikis.org is governed by an exhaustive nine-step admission pipeline. This sequence is designed to be mathematically rigorous, ensuring that the filter accuracy remains securely within the optimal operating regime1.

1. Preflight and Schema Validation: The Curator performs an initial pass to verify that the incoming JSON Memory Ticket conforms strictly to the UAIX.org standards. It checks the presence of a valid taxonomy kind, a proposed scope, and the necessary evidence references1.
2. Safety and Policy Evaluation: The event is evaluated against a boolean safety predicate. If the event contains prohibited execution commands, private network probing attempts, or attempts to assert unverified capabilities (such as biological equivalence), the predicate fails and the ticket is instantly discarded1.
3. Redaction and Privacy Filtering: To prevent cross-scope leakage, the payload undergoes sanitization. Personally Identifiable Information (PII), temporary secrets, session-specific tokens, and proprietary context are stripped from the event1.
4. Scope Appropriateness Assessment: The Curator calculates the scope predicate. Because a localized worker agent lacks global awareness, it may erroneously propose placing a project-specific procedure into the broad Agent Team scope. The Curator cross-references the event against the ecosystem directory to enforce a conservative mapping1.
5. Evidence Sufficiency Review: For memory targeting durable scopes (Team, Project, Repo) and utilizing high-stakes taxonomy kinds (Fact, Decision, Procedure), the Curator evaluates the evidence predicate. Claims lacking substantiation are downgraded to Session scratch or discarded outright1.
6. Global Deduplication and Equivalence Mapping: The sanitized event is projected against the existing memory manifold to test for equivalence relations. Information that is semantically redundant and provides no novel procedural utility is discarded to conserve computational resources and token budgets1.
7. Conflict Detection and Synthesis: The Curator compares the incoming event against heterogeneous sources. If Worker A previously claimed a specific environmental state, and the new event from Worker B asserts a contradictory state, the Curator initiates conflict resolution, attempting to synthesize the variance or escalating the ticket to a human review ledger1.
8. Terminal Disposition Mapping: Based on the cumulative outcomes of the prior seven steps, the Curator assigns one of the five write primitives—Append, Update, Deprecate, Conflict, or Discard—finalizing the admission decision1.
9. Formatting and Directory Promotion: If accepted into durable memory, the artifact is reformatted according to LLMWikis.org machine-readable templates, assigned appropriate UAIX trust labels, and pushed to the storage layer. Simultaneously, the overarching MATM directory is updated to reflect the new topological state of the "who knows what" network10.

8. LLMWikis.org Integration: Handbook Authority and Deployment Specifications

To fulfill the core objective of updating LLMWikis.org guidance, contributors must understand how the theoretical mechanics of MATM translate into the concrete structure of a wiki page. LLMWikis.org acts as the "handbook authority" for the ecosystem, owning the guidance for AI-readable wiki templates, trust labels, metadata structures, and safe reading paths10.

8.1 Structuring a New MATM Section or Companion Page

When adding a new page or section detailing MATM concepts to LLMWikis.org, contributors must adhere to strict editorial and structural constraints to ensure the output is safe for both human and agentic consumption. The public teaching anchor for any new architectural entry must serve as a "baseline reference" that establishes the first reader decision and core vocabulary without attempting to contain every subsequent implementation distinction8. The entry must utilize a Deployment Boundary Map or a Graph Reader-Action Map as its central artifact. The reader's primary job is to separate operational boundaries—such as transport, schema, moderation, memory firewalls, and consensus layers9. When drafting the page, contributors must apply specific source lessons: identifying the core knowledge, checking it against established standards, and keeping the strategic guidance explicitly tied to reader action8. Crucially, the guidance dictates that category metadata is not allowed to write the article by itself. The text must define the visible problem (e.g., "architectural scaling") and use foundational knowledge as the check that keeps the lesson grounded9. Contributors must systematically remove vague, dramatic, or repetitive wording, and ensure that the public lesson does not publish generic archive-summary frames when the lesson depends on strict graph relationships and standards8. The absolute boundary for any new MATM file is this: the page must never publish deployment architecture as evidence of live operator authority. It remains a unique, public teaching page in a categorized, archive-derived lesson set, explicitly denying any capability to grant protected access, execute rollbacks, or promote private sources8.

8.2 The Machine-Readable Directory and /ecosystem-overlay.json

Because MATM relies fundamentally on updating directories of expertise, an LLM Wiki must maintain a highly indexed, machine-readable map of its contents and capabilities. This is achieved through the /ecosystem-overlay.json companion file, which assigns every agent identity, wiki subspace, and external link to a specific, bounded domain lane21. For human readers, this overlay explains why a link leaves the site and which domain owns the subsequent step. For AI agents, it provides critical routing metadata. When an agent experiences a semantic inventory cache miss and cannot find relevant procedures in its local memory, it queries the ecosystem overlay to discover the correct specialist endpoint or machine-readable ontology expansion10. The overlay explicitly warns against namespace collisions—where agents might be pulled into unrelated external meanings—and prevents agents from merging claim authority between distinct sites simply because they are linked10.

8.3 Safe Read Orders and the /llms.txt Standard

Agents interfacing with an LLMWikis.org repository must not scrape or ingest data indiscriminately. The wiki must enforce a Safe Read Order that dictates exactly how machine readers parse transactive memory artifacts to prevent them from misinterpreting theory as executable commands10. This safe read order is managed via the /llms.txt index and specialized cognitive packet classes. The orientation flow mandates that agents must read boundary ledgers, domain overlays, human review triggers, and evaluation lab metrics before they access functional summaries or procedural trajectories22. The orientation documentation embedded within these files explicitly programs incoming consumer agents to prefer No-Op Behavior (disciplined refusal) when they encounter ambiguous transactive memory, cross domain lanes, or face a scenario where a claim appears stronger than its supporting evidence10.

8.4 The LLM Wiki Setup Wizard and Memory Packages

To operationalize these standards, infrastructure engineers utilize the LLMWikis Setup Wizard and the complementary UAIX AI Memory Package Wizard20. The Setup Wizard is specifically designed with a dual-audience architecture, generating outputs that serve both humans and agents simultaneously. It outputs local-first setup files, clear machine digests, prompt-security safeguards, and deep-linked boundary maps20. During provisioning, the Wizard automatically builds the structural foundation for the MATM scopes (Session, Project, Team, Repo) and establishes the UAIX schema compliance for all future Memory Tickets. By front-loading these architectural constraints into the wiki setup process, the Wizard ensures that new multi-agent deployments possess an inherent immune system against memory degradation from the moment of instantiation10.

9. Ecosystem Governance: Teleodynamic Posture and Epistemic Boundaries

LLMWikis.org does not operate in isolation; it is a foundational pillar within the source-routed Teleodynamic ecosystem20. The successful deployment of MATM requires strict adherence to the ecosystem's governing philosophy, which separates theoretical alignment, standards authority, semantic interpretation, and machine-readable knowledge surfaces into distinct, sovereign domains10.

9.1 Epistemic Firewalls and Domain Lanes

To prevent catastrophic agentic behavior, the Teleodynamic framework establishes epistemic firewalls. These firewalls physically and logically separate public theory, source documents, machine-readable JSON artifacts, UAIX schemas, and runtime execution systems into separate lanes, preventing static descriptions from transmuting into execution authority19. The ecosystem overlay defines these bounds explicitly:

• Teleodynamic.com: Owns the philosophical fulcrum and the core claim ledgers. It dictates that systems must justify their resource closure and forbids prohibited claims involving consciousness, biological autopoiesis, or unverified AGI10.
• UAIX.org: Serves as the standards authority, governing AI memory packages, project handoffs, and validator boundaries. It prevents arbitrary schema mutations10.
• LLMWikis.org: Holds the handbook authority. It owns the templates, metadata structures, source policies, and safe-read paths necessary to build the MATM infrastructure, but it is explicitly forbidden from executing runtime agents or overriding Teleodynamic claim statuses10.
• AIWikis.org: Functions as the reviewed long-memory archive, storing MATM evidence only after strict source-site review and the generation of checksum transfer packets20.

9.2 The Internal Resource Economy and Token Merging

A mature MATM implementation must integrate with the Teleodynamic concept of the "Internal Resource Economy." Memory retention exacts an ongoing toll measured across multiple multi-lane pressures: compute (inference and indexing costs), review (human oversight burden), governance (public-claim risks), uncertainty (ambiguity limits), and memory (dependency and retention burdens)19. Every transactive memory artifact must achieve "resource closure," justifying its creation and ongoing maintenance costs against its utility19. In complex interactive environments generating long video or temporal sequences, the compute lane faces severe pressure from quadratic attention complexity and massive KV-cache footprints. While the Memory Curator governs the semantic scope of memory, the infrastructure must simultaneously employ metadata-guided token reduction techniques. Utilizing intrinsic spatial and temporal metadata—such as codec residual data or Group of Pictures (GoP) packet sizes—systems can dynamically allocate token budgets, merging redundant tokens in background areas while preserving critical foreground trajectories25. This architectural synergy between semantic memory curation and mechanical token compression allows the LLM backbone to process vast procedural histories without exceeding resource bounds or sacrificing multi-layer attention stability25.

9.3 Slow-Loop Operators and Continual Learning

While execution agents operate in a fast loop—making immediate API calls and generating tactical outputs—the Memory Curator Agent and the LLMWikis.org governance mechanisms operate asynchronously in the slow loop19. Slow-loop operators execute deliberate, resource-aware structural actions on the transactive memory graph. These actions include splitting a bloated memory category, merging redundant procedural distinctions, retiring stale structures, or executing a no-op when an edit is unjustified19. By operating in the slow loop, the governance layer ensures that the transactive memory system adapts to environmental pressures while actively maintaining its teleodynamic organization. As agents generate, curate, and consume interaction trajectories, the system organically compiles a highly reliable, population-level corpus of procedural knowledge. When localized MATM entries reach absolute maturity and stability, they undergo a final slow-loop evaluation gate, are bundled with cryptographic checksums, and are transferred to AIWikis.org for permanent archival20. This source-routed progression ensures that volatile operational memory is continuously distilled into universal reference material, driving recursive, population-level improvement without the risk of knowledge collapse.

10. Implementation Roadmap for LLMWikis.org Contributors

For contributors tasked with expanding the LLMWikis.org repository to include MATM specifications, the following operational roadmap must be followed to ensure compliance with ecosystem standards:

1. Establish the Public Claim Ledger: Before drafting specific MATM implementation guides, map the proposed functionality to the Teleodynamic Governance Ledger matrix. Confirm that the page does not inadvertently transfer authority between sites or imply that a standard template grants runtime execution capabilities10.
2. Define the Deployment Boundary Map: Visually and structurally separate the transport, schema, moderation, memory firewall, and consensus boundaries. Use this map as the primary teaching artifact, ensuring readers understand the exact architectural constraints of the Memory Curator Agent before examining specific JSON schemas9.
3. Codify the Taxonomy and Scopes: Explicitly document the Nine-Kind Memory Taxonomy and the Four-Scope Partition model within the wiki templates. Provide clear, machine-readable examples of Memory Tickets, demonstrating how an agent must classify an event as a "Decision" versus a "Hypothesis," and the evidentiary requirements for each1.
4. Implement Safe-Read Metadata: Ensure the new section is fully integrated into the site's /llms.txt and /ecosystem-overlay.json structures. Apply UAIX trust labels and embed strict no-op dominance instructions so that subsequent crawling agents recognize the page as bounded handbook guidance, not executable code10.

By adhering to these rigorous architectural, mathematical, and philosophical specifications, LLMWikis.org will successfully operationalize Multi-Agent Transactive Memory, providing the definitive blueprint for resilient, self-maintaining agentic knowledge systems.

Works cited

1. agentlas-ai/agent\_memory\_curator\_agent: Memory Curator Agent for scoped memory governance in multi-agent workflows. \- GitHub, https://github.com/jeongmk522-netizen/agent\_memory\_curator\_agent
2. Multi-Agent Transactive Memory \- arXiv, https://arxiv.org/pdf/2606.19911
3. Multi-Agent Transactive Memory \- arXiv, https://arxiv.org/html/2606.19911
4. \[2606.19911\] Multi-Agent Transactive Memory \- arXiv, https://arxiv.org/abs/2606.19911
5. Stop letting your worker agents write to memory directly : r/LangChain \- Reddit, https://www.reddit.com/r/LangChain/comments/1to9rlq/stop\_letting\_your\_worker\_agents\_write\_to\_memory/
6. Memory Curator Agent a governance layer for memory in multi-agent systems \- Reddit, https://www.reddit.com/r/artificial/comments/1to9p3u/memory\_curator\_agent\_a\_governance\_layer\_for/
7. Should worker agents write memory directly? A curator-agent pattern I am testing \- Reddit, https://www.reddit.com/r/AI\_Agents/comments/1tly23u/should\_worker\_agents\_write\_memory\_directly\_a/
8. Baseline Reference for Graph Llmwikis Reader-Action Map \- NeuroWikis Public Wiki, https://neurowikis.com/public-wiki/wiki-entry-e9947b23f64edd3e6d/
9. Strategic Evaluation and Architectural Roadmap for Source-Governed AI Knowledge Systems: Baseline Reference for Deployment Boundary Map \- NeuroWikis Public Wiki, https://neurowikis.com/public-wiki/wiki-entry-03e3b3f2412b04fe39/
10. Teleodynamic Ecosystem Governance Ledger, https://teleodynamic.com/ecosystem-governance-ledger/
11. Transactive memory \- Grokipedia, https://grokipedia.com/page/Transactive\_memory
12. System Breakdown: The Role of Mental Models and Transactive Memory in the Relationship between Acute Stress and Team Performance \- AOM Journals, https://journals.aom.org/doi/10.5465/amj.2006.21794674
13. Transactive memory directories in small work units | Personnel Review \- Emerald Publishing, https://www.emerald.com/pr/article/33/4/446/458960/Transactive-memory-directories-in-small-work-units
14. A Computer Network Model of Human Transactive Memory | Social Cognition, https://guilfordjournals.com/doi/10.1521/soco.1995.13.3.319
15. Should worker agents write memory directly? A curator-agent pattern I am testing \- Reddit, https://www.reddit.com/r/openclaw/comments/1tly13c/should\_worker\_agents\_write\_memory\_directly\_a/
16. 1 Simulating the Role of Transactive Memory in Group Performance1 Yuqing Ren Dept. of Social & Decision Sciences \- University of Warwick, https://warwick.ac.uk/fac/soc/wbs/conf/olkc/archive/olk4/papers/ren.pdf
17. agent\_memory\_curator\_agent/docs/memory-taxonomy.md at main, https://github.com/jeongmk522-netizen/agent\_memory\_curator\_agent/blob/main/docs/memory-taxonomy.md
18. agent\_memory\_curator\_agent/agent.md at main · agentlas-ai, https://github.com/agentlas-ai/agent\_memory\_curator\_agent/blob/main/agent.md
19. Teleodynamic Core Concepts, https://teleodynamic.com/teleodynamic-core-concepts/
20. Teleodynamic AI Resources and HTML Sitemap, https://teleodynamic.com/resources/
21. Ecosystem overlay and domain authority boundaries \- Teleodynamic AI, https://teleodynamic.com/ecosystem-overlay/
22. AI Agent Start: Safe Read Order and Handoff Boundaries \- Teleodynamic AI, https://teleodynamic.com/agent-start/
23. Teleodynamic AI Summary for Machine Readers, https://teleodynamic.com/ai-summary/
24. Teleodynamic Intake Synthesis, https://teleodynamic.com/teleodynamic-intake-synthesis/
25. MeToM: Metadata-Guided Token Merging for Efficient Video LLMs Supplementary Material \- CVF Open Access, https://openaccess.thecvf.com/content/CVPR2026/supplemental/Wu\_MeToM\_Metadata-Guided\_Token\_CVPR\_2026\_supplemental.pdf
26. MeToM: Metadata-Guided Token Merging for Efficient Video LLMs \- CVF Open Access, https://openaccess.thecvf.com/content/CVPR2026/papers/Wu\_MeToM\_Metadata-Guided\_Token\_Merging\_for\_Efficient\_Video\_LLMs\_CVPR\_2026\_paper.pdf