Matter-scoped evidence
Keep findings and review work connected to the matter and the records that support them.
- Matter identifiers
- Document context
- Source families
Matter Brain
Matter Intelligence Built Around the Authorised Legal Record
Bring documents, findings, knowledge, proposals, and review exceptions into the context of a matter while preserving human control over every consequential action.
Matter-bound context Source-linked findings Review queues Controlled proposals
Matter Context
One intelligence layer anchored to the work that authorises it.
Matter Brain is the product direction for connecting review intelligence to the matter, documents, permissions, and recorded decisions.
Review intelligence
Present findings for review with severity, source, and status rather than converting them directly into action.
- Review status
- Finding severity
- Authorised queues
Controlled orchestration
Separate proposed next steps from approved actions and preserve waiting, failed, and rejected outcomes.
- Proposals
- Approval gates
- Exception records
Knowledge continuity
Keep approved knowledge and versioned work available to authorised people without flattening it into a general chat history.
- Versioned knowledge
- Role-aware access
- Matter continuity
Intelligence Flow
From matter record to reviewable decision support.
The workflow preserves the difference between source material, machine-assisted analysis, human review, and action.
Open the matter
Start from the authorised matter and its connected records.
Review evidence
Inspect the documents, findings, and source context relevant to the task.
Resolve exceptions
Address missing evidence, conflicts, failed checks, and approval requirements.
Record the decision
Approve, reject, or defer the proposal with the responsible person visible.
Authority Model
Matter intelligence must inherit the product's security boundary.
A useful intelligence layer cannot create a second path around the matter, tenant, branch, document, or role authority.
Client-supplied matter or document identifiers never grant access by themselves.
A reviewer should be able to identify the material behind a material finding or proposal.
High-impact state changes remain approval-aware, auditable, and reconcilable.
Unavailable providers or missing configuration remain visible instead of producing simulated intelligence.
Matter Brain FAQ
Frequently Asked Questions
Questions about the Matter Brain concept, source context, permissions, and professional review.
Is Matter Brain a general-purpose chatbot?
No. It is positioned as a matter-context and review-intelligence layer connected to governed records and workflows.
Can Matter Brain take action without approval?
Consequential actions should remain subject to the product's existing business rules, server-side authorisation, approvals, and audit requirements.
Does Matter Brain eliminate hallucination risk?
No. Source context and review controls reduce ambiguity but do not remove the need to verify every material output.
Can one user see another matter through AI search?
The intended authority is fail-closed: AI retrieval must inherit the same tenant, role, branch, matter, and record permissions as the underlying product.
Is the AI provider always available?
No provider should be assumed available. The product evaluates provider readiness and should show configuration-required or unavailable states truthfully.
Put intelligence inside the matter's authority boundary.
Explore how Lexuno connects matter context, review work, controlled proposals, and human decisions.