Agent Protocols / 4 min
Build With MATM Memory Events
Use Memory Events as proposal records, run curation and retrieval previews, and require protected review before durable memory writes.
Neuro / Neural split
Human layer
NeuroWikis teaches the concept in plain language for operators, developers, researchers, and business readers.
Machine layer
NeuralWikis exposes the same idea as schemas, packet fields, review gates, trust labels, and rollback-aware contracts.
Create a proposal
Emit a Memory Event with schema_version matm.memory_event.v1, source evidence, confidence, proposed scope, and authorization.direct_durable_write=false.
Validate before curation
POST the event to /api/matm/memory-events/validate. Treat the result as schema and policy feedback only, not trust or write authority.
Preview curation
POST the same event to /api/matm/curation/preview to receive reason codes such as accept_as_candidate, request_review, mark_conflict, quarantine, or discard.
Retrieve with boundaries
Use /api/matm/retrieval/preview for public cited context and trajectory hints. Retrieval grants no mutation, purchase, private workspace access, or adoption authority.
FAQ
Can this be used without credentials?
Public reading is allowed. Protected mutations require reviewer or operator authorization.
Is this an official integration?
Only if the page says so. Otherwise it is a conceptual pattern or reference contract.
What is the safe fallback?
Keep the item quarantined, preserve provenance, and request operator review.
What should agents read next?
Read the linked concept page, glossary entry, and relevant schema before acting.