Security
Built for the controls your review asks about.
Everything on this page is enforced below the interface and already in force; nothing is aspirational.
- Role-based access control
- Permissions resolve per user; scope is enforced in the database, not the interface.
- Matter-level isolation
- An attorney sees only assigned clients. Views that cross the isolation boundary return metadata only: stage and movement, never document content.
- Immutable audit trail
- Append-only event records on every matter. Not access logs: a substantive account of what was proposed, what was approved, and what was overridden.
- No model training on client work
- Client content is not used to train models.
- Document lifecycle
- Private storage with time-limited signed access, and a single filing path for every document.
The architecture behind the controls
Scoped at the data layer, not at the interface.
An unassigned attorney sees an empty workroom because the query returns nothing, not because a screen hid it. That distinction is the whole of our access model, and it is the one worth checking before you trust any of the rest.
Your work is not our training data...
- Client matters are never trained on
- No disclosure, specification, claim set, or attorney edit is used to train or fine-tune a model. Not ours, and not a third party's.
- Learning stays inside your firm
- The system learns drafting preferences from the redlines you accept. What it learns is scoped to the firm that taught it and never leaves it.
- No shared context between clients
- One client's matter is never in context while another's is being drafted. Retrieval is scoped to the matter you have open.
Access is enforced where the data is...
- Scoped at the data layer
- An unassigned attorney sees an empty workroom because the query returns nothing, not because a screen hid it. An interface bug cannot widen access.
- Workspaces are issued, not bought
- A client works in a workspace your firm opens inside your matter. Access ends when you end it.
- Encrypted in transit and at rest
- TLS 1.2 or higher in transit, everywhere. AES-256 at rest for stored matters and their attachments.
The record is the evidence...
- Append-only
- Every consequential act writes an event. Nothing is updated in place and nothing is deleted, including the decisions you would rather had gone differently.
- Failures recorded as failures
- A run that failed is recorded as having failed. It is not retried quietly until it produces something that looks like an answer.
- Portable when you want it
- The record exports with its decisions, overrides, and the reasons attached to them. It is yours before it is ours.
The supervision gates
Where the system stops and waits for a person.
Every gate can be overridden by a person, on the record; none can be overridden silently. The same catalog is published on the architecture page.
| The gate | What triggers it | How to override | What gets recorded |
|---|---|---|---|
| No search run before drafting | A specification is requested with no prior-art search on the matter. | Proceed without a search, stated explicitly. | The draft is marked as written in ignorance of the art, with the choice attributed. |
| Knockout reference found | A located reference reads on the claimed subject matter. | Continue anyway. | The finding, the decision, the person, and the timestamp, and the card arrives first in counsel's queue. |
| Unverified date on a reference | A date could not be read from the document itself. | Accept the date as stated. | The date keeps its unverified rank wherever it is later relied on. |
| Filing over open findings | A filing is attempted while findings remain unresolved. | File anyway, on the record. | An event naming each finding that was overridden. |
| Registry unavailable | The Office does not answer. | None: the step waits. | The unavailability, not an empty result. |
| Automated write proposed | The assistant intends to change a matter. | Human confirmation, per change. | The dry run, the confirmation, and the resulting change as separate events. |
Three refusals have no override, because they are not judgment calls. You cannot reorder paragraphs after filing, because the Office holds those numbers. You cannot edit the document from the review surface once the drafting room owns it. And prosecution tools do not appear until there is an office action to respond to.
Changelog
- 2026-08-16Catalog published. Six gates listed; three refusals stated.
Entries are appended, never edited away.
Single sign-on, directory provisioning, and certification status are stated in the security packet supplied during review, so the answer you get is the current one. We list nothing here that is not already in force.
If your review needs something not listed here, ask. We would rather answer it than have you assume.