02 · The matter brain
Change one fact. See what it moves.
Every document, person, obligation and decision lands in one matter record with its source attached. When something changes, the record can say which work was standing on it.
Some source state could not be read. This review is incomplete, and says so.
The question in the room
“This deposition contradicts our theory. What else in the file is now wrong?”
The change set, the approved-workflow impact and the affected-work review run today. Deeper kernels in the same engine, including proof debt, action readiness and decision memory, are built and tested but are not yet invoked at runtime.
How it works
The mechanism, not the promise.
A record that knows what it is made of
The matter is modelled as objects and the relations between them: assertions, claim elements, contradictions, decisions, gaps, workflow steps, artifacts and external effects, joined by relations such as depends on, supports, contradicts, governs and gates. Every reference carries a version and a content digest.
What changed, proved by version and digest
Two frozen matter snapshots are compared into a change set, and the change set is traversed into a bounded impact manifest naming the affected objects, the facets touched, and the action each now requires.
Work that was waiting on something that moved
When an artifact's pinned sources change underneath it, the decision that was waiting on it surfaces on the daily board as work affected by a change, with the moved source named.
Every claim resolves to a page
ShippedEntities, relationships and facts resolve back to the chunk, page and document they were lifted from.
backend/src/lib/rag/provenanceResolver.ts
Two people, one name
ShippedA namesake signal vetoes a merge and records the pair for an attorney to settle, because welding two legal persons together destroys one of them.
backend/src/lib/rag/knowledgeGraph.ts
A wrong-matter detector
ShippedA freshly ingested document sharing no party with the matter raises a high-priority task before its facts can reach the graph, the valuation or the client portal.
backend/src/lib/rag/wrongCaseDetector.ts
Retrieved text is data, never instruction
ShippedRetrieved chunks are wrapped as source material and screened for instruction-like phrases before a model sees them.
backend/src/lib/rag/retrieve.ts
A firm graph that fails closed at the wall
ShippedCross-matter reads are scoped by the ethical-wall unit, and a failed wall lookup returns empty rather than whole.
backend/src/lib/rag/firmGraph.ts
Refusals
What it will not do, and why.
- Answer the question with fewer than two snapshots.
- It says two frozen snapshots are required before it can prove what changed. That is a different sentence from nothing changed, and the difference is the product.
- Guess once the comparison exceeds its budget.
- Past the bounded lineage budget it reports that workflow impact was not guessed. No approved workflow depending on this snapshot is a separate answer with its own wording.
- Read unreadable source state as unchanged.
- A pin whose source cannot be read is recorded unreadable, the review is marked blocked, and the screen says to treat it as incomplete.
One record
Nothing here stands on its own.
What feeds it
- Intake
- Every ingested document
- Discovery findings and depositions
What it feeds
- Valuation
- Drafting
- Deadlines
- The daily board
Limits
What this does not establish.
- At very large corpora the graph is a deliberate sample, and the coverage line says which tier you are reading.
- An impact manifest reports itself as partial when a traversal bound is reached, rather than truncating quietly.
Check the work before you believe it.
Run a sample manifest in your own browser, or read where publication refuses for want of evidence.