The LLMWikis governed MATM profile is a practical implementation profile for teams that want agent-generated experience sharing without direct worker writes. It is not a universal standard, conformance program, or certification.
Profile Rules
- MUST keep worker agents proposal-only for durable memory. Workers emit Memory Events; they do not write durable records directly.
- MUST keep hidden chain-of-thought and private reasoning out of durable-memory requirements.
- MUST use the four core durable scopes: session, project, agent_team, and agent_repo. Discard is a disposition sink, not a durable scope.
- MUST preserve source, status, scope, sensitivity, owner, evidence, and review metadata before retrieval treats a record as usable.
- SHOULD add deterministic schema, redaction, dedupe, conflict, and source-quality checks before model-assisted curation.
- SHOULD label user_identity, organization, and cross_organization memory only as namespaced optional extensions with stricter privacy rules.
- MAY use centralized, federated, or hybrid topology when the deployment owner can justify privacy, availability, latency, and conflict tradeoffs.
Implementation Levels
| Level | Name | Required artifacts | Claim allowed |
|---|---|---|---|
| MATM-H1 | Handbook-ready | Roles, boundaries, taxonomy, scopes, source policy, and no-runtime boundary. | The team has designed governed MATM. |
| MATM-H2 | Proposal-and-curation-ready | Memory Event schema, quarantine, curation reports, audit trail, direct-write prohibition. | Workers can emit proposal-only Memory Events. |
| MATM-H3 | Retrieval-ready | Reviewed records indexed with scope, status, evidence, provenance, citations, and abstention rules. | Consumers can retrieve reviewed scoped memory. |
| MATM-H4 | Evaluated deployment | Metrics for routing, leakage, evidence, redundancy, conflicts, utility, latency, cost, privacy, review burden, and adversarial behavior. | The deployment has measured field behavior under its own assumptions. |
Artifact Map
| Artifact | Level | Route or bundle path |
|---|---|---|
| MATM_POLICY.md | H1 | llm-wiki/matm/MATM_POLICY.md |
| Memory Event schema | H2 | llm-wiki/matm/schemas/memory-event.schema.json |
| Curation report schema | H2 | llm-wiki/matm/schemas/curation-report.schema.json |
| Transactive directory schema | H3 | llm-wiki/matm/schemas/transactive-directory.schema.json |
| Retrieval request/response schemas | H3 | llm-wiki/matm/schemas/retrieval-*.schema.json |
| Evaluation plan | H4 | llm-wiki/matm/EVALUATION_PLAN.md |
Non-Claims
Adopting this profile does not prove production readiness, security approval, privacy compliance, UAIX conformance, benchmark superiority, certification, or that LLMWikis operates the runtime. The deployment owner must implement, test, and approve its own system.