Why
Hosts need one place for many kinds of content about one subject.
Memorix answers that with one envelope, one HTTP service, and one Studio UI.
The gap
What hosts invent without a platform
Without a shared contract, every product reinvents list columns, write shapes, relationship copies, and operational ledgers — then agents guess the next step.
- Writes carry an expected revision; stale writers cannot overwrite newer data.
- Unresolved targets are retained and shown — not silently dropped.
Before
- Flattened subject blobs
- Copied neighbor payloads
- Writes without revision safety
After
- ✓One kind of content per subject
- ✓Four-field relationships
- ✓Revision-safe writes + human control
Memorix Platform Overview — Developers
Audience: Engineers integrating another product with Memorix (HTTP API or @x12i/* packages). Twin: Builders version Scenario: Non-cyber opx · fresh sandbox* · agentIds: ["opx"] — see _shared/opx-scenario.md. Site: https://docs.memorix.x12i.com · Hard rules
Subject and content
How to read: Read left to right. Subject is the stable id; content kinds attach; relationships point to neighbors; abstracts compose views.
Text alternative: A stable subject holds multiple content kinds; relationships link subjects; abstracts project unified views at read time.
PlantUML source
@startuml
rectangle Subject as S
rectangle "snapshot" as C1
rectangle "workflow" as C2
rectangle "analysis" as C3
S --> C1
S --> C2
S --> C3
@enduml