Descriptor-driven operational memory
Memorix — one kind of content about one stable subject
Composed by recordId, navigated by four-field relationships, projected by virtual abstracts. One HTTP service, one Studio UI, revision-safe writes.
$ npm install @x12i/memorix-sdk
Knowledge for agents: npm i -D @x12i/memorix-docs
Host products keep authority. Memorix owns the data contract.
One memorix-record/2 shape for every content kind.
Every request names orgId and agentIds — deliberate isolation.
Revision-safe writes and human-gated intelligence proposals.
The positioning
Tell the story before the feature list.
Host products need one place to store many kinds of content about the same subject, relate different subjects without copying neighbor payloads, and operate runs with human control.
Why it exists
# Memorix Platform Overview — Developers
What is different
**Audience:** Engineers integrating another product with Memorix (HTTP API or `@x12i/*` packages). **Twin:** [Builders version](../builders/BOOK.md) **Scenario:** Non-cyber `opx` · fresh `sandbox*` · `agentIds: ["opx"]` — see…
What you get
## Install (start here)
Writes carry an expected revision; stale writers cannot overwrite newer data.
Learn more →A relationship definition is metadata describing allowed links — not a stored edge on a record.
Learn more →Sources feed Memory; Memory holds durable product records.
Learn more →$ memorix integrate