Skip to contentThe claims register is public. 27 verified, 7 struck.

Memory that shows its working.

The Brain is the knowledge layer the governed workforce draws on. Every assertion in it is designed to carry its provenance: the origin it came from, and a trust grade. This page separates what is live today from what is design intent, and says which is which.

The governed workforceThe research behind it

The design centre

Provenance is the design centre. What was known, and where the knowing came from.

An assertion here is not a bare string. The design gives each one three things, and the day something goes wrong is the day all three are asked for.

The research behind it

An origin

Each assertion is designed to carry where it came from: the document, feed or governed action behind it. Not a bare string.

A grade

How far the assertion is trusted, stated rather than implied, so a better-graded assertion can be told from a worse one.

A place in the record

When an agent acts on what it knows, the record of that action is designed to show what was known, and where the knowing came from.

The question is never just what the system did. It is what it believed, and why.

Live and design

What is live, and what is design. The line between them is drawn, not implied.

We would rather be exact than impressive. When any part of the design becomes live behaviour, it moves to the other side of this line with a verification record beside it.

Assertions name their origin. Ungraded knowledge never executes.

Read the research behind the Brain
Traced to an origin, or not counted

brain

The line, todayon the register
  • Recall of prior governed context, on every runLive
  • Pack rule digest recomputed at boot, refuse on mismatchLive
  • Assertions that expire rather than lingerDesign
  • A better-graded assertion outranks a worse oneDesign
  • Revision in the open when evidence contradictsDesign
  • Erasure requests across the knowledge layerDesign
Live, with verification records

Agents recall prior governed context on every run. The recall sits inside the execution path, which is why the sentence says every run.

The industry pack is load-bearing: at boot the governance layer recomputes the pack's rule digest and refuses to serve if it does not match. The failure mode is refusal, not a warning in a log.

The packsThe kernel
Design intent, stated as such

The layer is designed so that an assertion carries a period of validity and expires rather than lingers; so that evidence carries a grade and a better-graded assertion outranks a worse one; and so that when new evidence contradicts old, the older assertion is revised in the open rather than overwritten in silence.

It is also designed to support erasure requests across the knowledge layer, so that when a person's data must go, the assertions derived from it can be found and removed.

None of that is claimed as live behaviour.

Plainly

Plainer than most, on purpose

Bring one workflow where an agent's memory worries you. We will show what stands in front of it today, and what does not yet.

Book a demoWhere we are