Solutions · Registry
Canonical, never rigid.
One record, kept as the source wrote it. The layers your teams work in are built on top: views over the core, never copies that drift.
A fixed literal core · layers as views · traceable to the quote
Three working layers, one literal core. Every layer reads down to the same words.
01 · The core layer
As written, kept written.
A value enters the registry with the exact words that carried it, and keeps them.
Everything added afterwards is derivation, never replacement. The normalised amount, the account code, the classification tag: each names the rule that produced it and sits beside the original, not over it. Ten years on, clause 14.2 still reads the way the contract wrote it.
02 · The layers
The layers that emerge.
Kept entries sort into the views a working day needs. Every layer is a view over the core, never a copy that can drift.
Each placement is a decision on record, not a shuffle.
By category
Fact, opinion, internal, external, author. Every entry is layered by what kind of statement it is and who made it, so a search for facts never surfaces an aside from a mail thread as if it were one.
By value
Urgent or archive, core or transactional, tone, resolved or unresolved. The layers that decide what today's queue holds and what is allowed to sleep.
By what an agent needs
An agent working the estate assembles its own web of decision layers over the same core: the entries it watches, the thresholds it acts on. Its view, your record.
03 · Search
Search by category. Land on the quote.
A query names the layers it wants. What comes back is the entry itself: the quote, its source, the layers it carries.
No re-reading a returned document to find the line. The propped fire door, the expiring certificate: each answer arrives already open at the words that earned it, with the trail back to the file attached.
“fire door propped open
“forklift · expires 2026-03-01
2 entries matched. Each carries its quote and its layers.
04 · Versioned change
Change ships as a version.
Nothing resets, nothing retrains
The layer does not learn your data into a model. It records it under written rules, so keeping ten years of records makes you auditable, not exposed.
Change is a new version
A new sorting pattern, a new match rule, a new retention term: each ships as a configuration version. The old version stays runnable beside it, so last year's view of the record is still last year's view.
Both answers stay defensible
Ask the same question under version 4 and version 5 and you can see both results, and the written rule that changed between them.
05 · The record
A record you can put under oath.
Every value carries its quote
A record entry is a value plus the words, frame or cell that earned it. The layer holds no orphan numbers.
Any view re-runs byte for byte
A report, an entity page, an answer: each re-runs on demand and lands identically, for an auditor holding a year-old question.
Retention on instruction
The layer stores decisions and quoted evidence, not profiles. Deletion follows your instruction, and the deletion is itself recorded.
Ask the record in plain language: Sokros Copilot →
Bring the estate nobody can query.
The shared drives, the mailboxes, the database exports. One briefing, one slice of your estate landed in the registry and asked in front of you.
A 30-minute briefing: one estate slice scoped, a gated pilot plan.