Skip to content
BRONLitigation.Held together.

Public information

The matter brain: capabilities and limits

Product reference. Read the supported work alongside its review requirements and limits.

Last updated September 22, 2026.

Return to the matter brain

Current availability: 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. Every element definition in the record is a cited machine draft marked as one, and every element link was written by the extractor, so a proof state is a reading of what has been recorded rather than an attorney's ruling on the law of the forum.

Capabilities

Everything arrives with its source

  • Every claim resolves to a page

    Shipped

    Every entity, relationship and fact resolves to the chunk, page and document behind it, bridged by the verbatim quote the extractor stored. A tie goes to the chunk whose page range holds the recorded page. A quote that cannot be placed is counted, not guessed.

  • Retrieved text is data, never instruction

    Shipped

    Retrieved chunks are wrapped as source material and screened for instruction-like phrases before a model sees them. That reduces prompt-injection risk. It does not turn retrieved text into something the model may take orders from.

  • Four lanes, and a lane that failed is not a lane that found nothing

    Four lanes: vector, lexical, exact-string for statute cites and Bates numbers, and a graph lane that walks one hop and feeds those names back. Lanes fuse on rank order. A failed lane is named; a corpus not shown to be one embedding space is refused.

  • Every dollar figure in the record, with no model in the path

    Backend only

    Amounts and dates are parsed into a ledger, so every payment returns with its quote and page. A regex and a join, checkable row by row. Amounts fire only on an explicit currency marker; a re-ingest replaces a source's rows rather than doubling them.

People, and not confusing two of them

  • Two people, one name, and one record for each

    Shipped

    A namesake signal vetoes a merge and records the pair for an attorney, so a record both client and adverse is raised rather than split. The directory holds one record per person or company, wall-subtracted on the server and paged past the thousand-row cap.

  • A person is not the company that carries their name

    Shipped

    Two vetoes guard the deterministic merge. Alan Voss and Alan Voss Consulting shared two tokens of three and collapsed into one node; the same arithmetic keeps negligence apart from gross negligence. A company's matters come from an attorney's recorded attachment, never an email domain.

  • A wrong-matter detector, and another case's facts

    Shipped

    A newly ingested document sharing no party with the matter raises a task before its facts reach the record. On one matter, 13 of 63 documents were cited opinions minting 378 entities of a 1,353-entity graph. The screen reads extracted text and logs every exclusion.

What is established, what is disputed

  • Two lists and a denominator, never netted

    An element carries what supports it beside what defeats it, with quote, document and page, capped at six a side and the full count reported. The sides are never averaged, the forum's element count ships with every read, and a withdrawn fact is never offered.

  • Five rungs, and neutral is a reading while unknown is a silence

    Each side climbs five rungs, from nothing has looked through a directed link, so an unexamined side never renders like an empty one. Direction is one of four: neutral is an affirmative reading, unknown is a silence, and nothing in the writer can produce neutral.

  • Who drew the edge, on the face of it

    Every edge is classed derived, asserted or authored, and an unrecognised basis classes as authored. Today, element definitions are cited machine drafts marked as drafts and every link came from the extractor, so a proof state is a machine reading of a machine-drafted list.

When something changes

  • What changed, proved by version and digest

    Two frozen snapshots are compared into a change set naming what moved and the digest on each side, then traversed into a manifest naming each affected object and the action it requires. A manifest that hit its bound says so rather than reading smaller.

  • Work that was standing on something that moved

    A draft pins the source versions it was built on, and when those pins move the approval or client draft surfaces on the daily board with the moved source named. An unreadable pin blocks the review; a scan bounded at 500 pins reports itself partial.

What the matter says when you open it

  • The fact record answers in four states, and two of them are not zero

    One bounded read serves every matter summary, in four answers: it holds facts, it holds none, the migration is not applied, and the read faulted. The last two are never rendered as no facts. Only the function that logs posture may write it.

  • A standing brief with a floor under it

    The deterministic composition is the floor; the model polish falls back to it on any failure, and a column records which of the two you are reading. Agenda items derive at compose time from the task queue, so a badge and a brief cannot disagree.

What the firm knows across matters

  • A firm graph that fails closed at the wall

    Shipped

    Cross-matter reads are scoped by the ethical-wall unit, and a failed wall lookup returns empty rather than whole. The banked corpus is read in its own lane, never fused into this matter's retrieval, and a lane that fails returns its reason, not an empty list.

  • A bank the firm opts into, and a scrub that refuses

    Work product reaches the cross-matter corpus through two firm-administered switches, one for contributing and one for reading, with the per-matter opt-out left to the attorney. Text is scrubbed twice, and a known party token that survives refuses the bank rather than persisting a half-scrubbed document.

  • The client is the unit, and the hub shows the unfiled ones too

    One page answers for a client: every matter and phase, six money figures, a document rollup, portal access granted and revoked. Neither it nor the firm-wide document hub turns an unreadable or filtered read into a number, so a failed billing read prints no figures.

Limits

  • At large corpora the graph is a deliberate sample of the record, and the coverage line says which tier you are reading.
  • Element definitions in the record today are cited machine drafts marked as drafts, and every element link was written by the extractor. A proof state is a reading of what has been recorded, never an attorney's ruling on the law of the forum.
  • An impact manifest reports itself as partial when a traversal bound is reached, rather than truncating quietly.
  • The snapshot pair a change set is compared from is frozen when a workflow proposal is composed, so the change view answers for those matters and stays silent about the others rather than reporting stability.
  • The record is what has been ingested, extracted and recorded. It is not a representation that nothing is missing.

What BRON refuses

  • Read a link as support because it points at an element.

    A link carrying no recorded direction sits on its own rung and populates neither side. Linked and supported are different facts, and when the extractor starts recording direction the same code keeps telling the truth with no edit.

  • Store an unreadable reading as neutral.

    Neutral is an affirmative measurement and never a fallback. Every unreadable, absent, malformed or out-of-vocabulary value resolves to unknown, and no alias maps onto neutral, because an adverse fact called neutral is an adverse fact hidden.

  • Net the two sides into one number.

    An element can be well supported and contested at once, and those are two facts about it rather than one. There is no scalar on an element and no field that could carry one, so nothing downstream can multiply a coverage figure by a dollar.

  • Offer a withdrawn proposition as an undisputed fact.

    A retired, merged-away or quarantined fact is not proof. Exporting one launders a proposition the attorney withdrew back into work product, carrying its record cites, into the statement a court reads.

  • Weld a person to the company that carries their name.

    The merge is canon-wins, so a wrong yes raises nothing for anyone to notice. It destroys the loser's attributes, repoints its edges, and the surviving row then feeds the conflicts scan. A refused merge leaves two half-populated records an attorney can reconcile, which is the recoverable direction.

  • Guess the page a quote came from.

    A quote that cannot be located inside the chunk that produced it is left unresolved and counted. A wrong chunk is a wrong page and a wrong page is a wrong Bates cite, which is a misstatement to a court.

  • Search a corpus it cannot show is one vector space.

    Two embedding models write the same width into the same column, so a mixed corpus throws nothing and returns a plausible wrong neighbour list. A refusal is loud. The alternative is silent, and took semantic search down for six days without a symptom.

  • Report a lane that failed as a lane that found nothing.

    A search that ran and matched nothing is a finding an attorney may rely on. An embedding outage or a failed lexical read is not, and a half-blind search rendered as an empty record is the sentence that gets relied on anyway.

  • Answer the change 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.

  • Read source state it could not fetch as unchanged.

    A pin whose source cannot be read is recorded unreadable, the review is marked blocked, and the screen says to treat the answer as partial rather than as a clean bill.

  • Show a firm directory when it cannot tell which firm you are in.

    A missing or ambiguous membership is an unresolved tenant, not a solo practice. An empty roster would say the firm knows nobody, and falling back to the signed-in owner's own rows would cross two tenants, so the read raises and the surface reports that it could not look.

  • Render a client's billing position it could not read as a zero.

    A tile carrying a dollar figure is how could-not-look reaches a partner as a settled number. The unreadable branch prints the words and no figures, and a source-text test keeps every tile out of it.

  • End a document list on a figure that was filtered for the reader.

    The total is the collection minus the rows read clearance dropped on the window just served, so paging on it stops one page short and leaves documents unreachable beneath a count that reads as everything. Termination is the separate fact of whether that window came back unfilled, and an absent header is unknown, which keeps offering.

Which elements are actually proved, what cuts against each one, and what moved underneath them last week?

Follow a fact back to its source and forward to the work that depends on it. Supporting evidence, contradictions and unread material stay distinct, so a changed source brings the affected work back into view.

Inputs

  • Intake and the engagement record
  • Every ingested document and production
  • Depositions and discovery findings
  • The attorney's own postures, element calls and merge decisions

Outputs

  • Valuation
  • Drafting and the citation gate
  • Deadlines
  • The daily board and the standing brief
  • Workflow proposals