Marrinn · The architecture · The Memory
The Memory.
One version of the truth, across systems you do not own. The Memory holds your own records, the outside systems you connect, and the context every previous build left behind — and it resolves them into one picture without copying anything and without overwriting anyone.
The same entity, in four systems at once.
Every business of any age has this problem, and almost nobody calls it a data problem. It looks like a reporting problem, or a compliance problem, or a reconciliation week at the end of every quarter. Underneath, it is the same entity living in several systems under names that never quite match.
An investment company is the clearest case, so that is the one written out below. The shape is identical for a hospital with one patient across four systems, or a contractor with one supplier across procurement, finance and the site log.
One investor, four spellings.
An investment company does not have a data problem in one system. It has the same entity living in several, under names that never quite match, and no single place that says which version is right.
- CRMAl Ahli CapitalRelationship manager, last contact, mandate notes
- Fund adminAl-Ahli Capital Co. KSCCCommitment, drawn, unfunded
- KYC fileAACC (Kuwait)Beneficial owners, ID expiry, risk tier
- Cap tableAhli CapitalHoldings across three vehicles
One investor record
Four source rows, one entity, and a named owner for every field. The CRM stays authoritative for the relationship. The register stays authoritative for the risk tier. The fund admin stays authoritative for the commitment. Nothing is copied and nothing is overwritten.
The capital call goes to the right entity
Four spellings meant four records, and a drawdown notice sent against the wrong one. One resolved investor means one distribution list, and a mistake that stops being possible rather than being caught later.
Concentration by beneficial owner becomes visible
The same ultimate owner holding through three vehicles looks like three unrelated positions in three systems. Resolved to one owner, the aggregate exposure is a number you can actually report to a risk committee.
The reporting cycle stops being manual reconciliation
The reason an investor report takes weeks is rarely the writing. It is the days spent agreeing whose figure is correct. When authority is settled once, in advance, the pack assembles from records that already agree.
An expired ID cannot hide behind an active client
The CRM says the relationship is live. The compliance file says the identification lapsed. Today nobody reconciles those until an audit asks. Here the contradiction surfaces the day it appears.
Five places a Squid gets what it knows.
The first fair question about any agent is what it actually knows about your business before it starts, and where that came from. There are four answers, and only one of them involves searching for anything.
They are deliberately different in kind. The records are current because they are never copied. The profile is stable because a person wrote it. The doctrine is authoritative because a named person is accountable for it. And the search is for the times a plain question has to meet content nobody indexed by hand.
The records themselves
The largest part is not retrieved at all. A Squid opens the module and reads the live row, the way a member of staff with a login would, and it sees exactly what that login allows. Nothing is copied into it, so nothing it reads can be out of date.
Your organisation’s profile
One page describes the business: sector, type, size, country, the regulatory frameworks you work under, your mission, and a free-text field for the context that never fits a form. It is carried into every question the AI is asked, so an answer is shaped by your organisation rather than a general one.
The doctrine a department keeps
How this department has decided to work, in prose, written by the manager who owns it: the materiality threshold, what gets escalated, the claim rules, what the brand never says. Versioned, superseded rather than overwritten, and it outranks whatever the model would have assumed. Where it is written →
A search that reads for meaning
Ask in plain language and the answer comes back with its sources named and ranked, rather than a list of keyword matches to work through. This is the one part that needs a model able to generate embeddings. Where the configured model cannot, the search is unavailable rather than quietly worse.
What happened on its own last run
The other four sources describe how the business works today. None of them says what this Squid already tried. So it reads the outcome of its own previous runs on the same subject — what it proposed, what was approved, what was rejected, what failed. Without it, an agent re-proposes a rejected action indefinitely and somebody turns down the same suggestion every week. It recalls only its own runs, under the same permissions that applied to the records, and it expires on the same retention schedule, because a memory that outlives the permission which created it is a leak.
All four inherit the rules on this page. Authority is per field. A disagreement surfaces instead of resolving itself. A source marked on-prem is never sent to a cloud model. And any figure a Squid hands you names the system it came from and the moment it was read.
The thing they argue about is not a record.
Resolving four spellings into one investor is the easy half. The harder question comes next, and a risk committee asks it in one sentence: what is our exposure to any single beneficial owner, across every vehicle. That number sits in no system. It is assembled from the cap table, the KYC file, the fund administrator and the CRM, and three of those did not come from us.
So a concept is declared once, here: what it is called, what it means in plain language, which records it is built from, and the rule that assembles them. After that it is one object, and every Squid, every report and every board pack reads the same one.
A name, a meaning, and a rule
A concept carries the name the business already uses, a definition in the words a person would say it in, the records it is built from, and the rule that assembles them. It is the difference between a number four people can produce and a number the four of them agree on.
The traversal is declared once
Hold thirty percent of a vehicle that holds forty percent of an asset and the exposure is twelve. No schema anywhere has that column. So either every analyst rebuilds the arithmetic in their own spreadsheet, or it is written down once and read the same way every time it is asked for.
Including the ones you did not buy from us
A concept can be defined over records in Marrinn together with records in the cap table, the fund administrator or the clinical system you already run, reached through the Ports layer. That is the case a specification cannot cover on its own, because those schemas were never written from it.
Against the rule that set it
Definitions move when a regulator moves a threshold. A concept keeps its versions and their dates, so a position booked in March is still read under the definition that was in force in March, rather than quietly restated under this year’s and reported as though nothing changed.
One object, every Squid
Finance’s exposure, compliance’s related party and sales’ client overlap and are not the same thing. Declared as concepts, that difference is explicit and each Squid binds to the definition it should. Left in prose, it stays a matter of opinion until an audit settles it for you.
A query answers a question, a concept settles one
A saved view is written by one person for one question, and the next person writes a slightly different one. Six months later there are four definitions of exposure in circulation and no way to know which of them the board pack used.
Concepts inherit everything else on this page. Each one names the systems it was assembled from and the moment they were read. Where two of its sources disagree, the disagreement is surfaced rather than averaged away. And a concept a Squid was not bound to is not in that Squid’s world, however plainly it is written down. How a Squid is bound →
Nothing is copied, and nothing is overwritten.
The usual approach builds a single master record and picks a winner for every field. That is why the master record is wrong within a month: the moment a system updates and the copy does not, the master is the least current version of the truth in the building.
Four rows, one entity
The records stay where they are, in the systems that own them. What The Memory adds is the link between them, so the four spellings are understood to be one investor without any of the four being edited.
Per field, not per system
The CRM is right about the relationship. The register is right about the risk tier. The fund admin is right about the commitment. Authority is set field by field, because no system is authoritative for everything it happens to store.
A disagreement is a finding
When two sources hold different values for the same field, that does not become a silent decision. It becomes an item on the board, with both values, both timestamps, and the named person who owns it.
Every figure names its source
A Squid citing a number says which system it came from and when it was read. A figure you cannot trace is a figure nobody will sign, which is why traceability is part of the answer rather than a report you can run afterwards.
Read-only, and field by field
Connect a source read-only and choose which fields it may see. The Memory reads what you allow and writes nothing back, so connecting a system carries no risk to the system.
Mark a source on-prem
A source marked on-prem is never sent to a cloud model. Combined with a private model running on your own hardware, the whole path stays inside the building.
Seven parts, one operating system.
Read the seven from the bottom and it is an operating system: a kernel, a data model, memory, a way to see, processes that do work, a place those processes meet people, and ports to everything outside.
The Kernel
The model, and it is your choice.
The Core
Every module on one data model.
The Lens
Where the records become an answer.
The Squids
The operators, and one can lead others.
The Handoff
Where an agent stops and a person decides.
The Ports
And it reaches what you already run.
The Memory is one of seven parts.
It sits between the core and the lens: the kernel is the model you choose, the core is thirty-five modules on one data model, The Memory is what they all agree on, and the ports are how it reaches the software you already run.