Skip to content
Arrange a meeting

Product reference

Record and exports: how it works

Follow the analysis, cited sources and approval into a fixed handoff. Check the original files against the export manifest while keeping the legal and evidentiary questions separate.

On this page

Return to record and exports

Availability

Available
Supported work
Hand over the versions, sources and decisions behind reviewed work, with fixed shared analysis and an export manifest recipients can check without an account.
Start with
A reviewed version, its sources and the recorded approval define the handoff. Select the material and recipient deliberately; internal strategy work product does not become client-visible simply because it is linked.
Key limit
A matching file shows the bytes are the ones recorded. It does not show that nothing is missing, or that the work is right.

Some capabilities have their own availability or configuration requirements, shown below.

Before you start

  • A reviewed version, its sources and the recorded approval define the handoff. Select the material and recipient deliberately; internal strategy work product does not become client-visible simply because it is linked.
  • To share a brief, the matter's owner makes a signed link. By default it expires after 14 days.
  • To export, the Firm page. A preview names included and excluded categories and known omissions. The manifest also records gaps discovered while reading the files.
  • To check an export, the files and the manifest. The recipient needs no BRON account, and the verifier runs offline.
  • To review a source correction, keep both versions and inspect recorded citations and the exact copies that cited them. Review the working draft separately before deciding what changes.
  • Collected bytes are retained by default. Destruction requires an enabled firm policy and an attorney's act at execution; there is no automatic destruction on a timer.
  • To let your own AI tools read the record, a key limited to the matters you name.

How it works

Carry the sources, exact versions and recorded decisions behind the handoff. Share reviewed analysis on a fixed link, or export the included matter records and document versions with a checkable manifest. A recipient can inspect supplied files without a BRON account.

Which version and sources did this recipient receive, and what can they check independently?

From reviewed work to inspectable handoff

  • Keep analysis attached to the version and sources

    A notice memo can carry both attributed accounts and the unresolved receipt question into a fixed shared version. Its sources and recorded approval make the handoff inspectable. A later correction calls for review and a new version rather than silently changing what the recipient saw.

  • Let the recipient check the supplied files

    The May 2 email and attachment can travel with the export manifest. A digest match checks those bytes against the export record. It does not establish receipt, reading, the legal effect of notice, admission at trial or whether other material exists.

What you hand over

  • A link that opens one fixed version

    The matter's owner can share a brief on a signed link that needs no BRON account. By default it expires after 14 days, and the owner can revoke it sooner. A later edit does not change what the link serves.

  • The brief and its sources, never the matter

    The link opens the brief and the documents it cites, never the rest of the matter. It allows no edits and no export. Each cited source is checked against any protective order on every read, and a brief citing a refused source is not served.

  • An export with its manifest

    Available

    An export carries current document versions, the included matter data as CSV files, a checkable audit trail and a SHA-256 manifest. Its timestamp status and any available OpenTimestamps proof travel with it. Excluded categories are named; this archive alone is not the entire client file.

  • A preview before the download

    An export starts with a preview of included categories, exclusions and known omissions. The manifest records further gaps found while reading files. An owner or admin can export the whole firm; staff can export a matter they can open.

  • Each citation carries its evidence

    Available

    For a filing, the manifest records a digest of each cited source, the exact words relied on, where they sit in the text, and a verdict. The format is published, so a recipient can build their own verifier in any language.

How the recipient checks it

  • A verifier that runs offline

    Available

    The verifier is MIT-licensed, depends on no other packages and runs offline against local files. It recomputes the coverage counts from each citation's verdict instead of trusting the totals written in the manifest.

  • An unread source is advisory, not verified

    A cited source that was found but never opened is recorded as advisory, never verified. A substantive defect, such as a quotation the source does not contain or a pin cite outside its pages, is recorded as failed.

  • Look up a digest without an account

    Available

    Anyone can paste a SHA-256 digest on the verify page and see whether it was recorded, when, and how strong its timestamp proof is, in plain words. The answer names no matter, party, title or file.

What the record keeps

  • Review a correction against the work that relied on it

    A corrected source stays beside its earlier version. Open recorded citations and their exact cited copies to inspect known reliance. A correction does not rewrite an approved memo; counsel reviews the working draft and decides what changes. Unrecorded reliance may exist.

  • An activity log checked three ways

    Available

    Approvals and other key acts are added to a log that is never edited and can be checked for tampering. BRON checks that no entry changed, that none is missing or out of order, and that the latest has a timestamp proof.

  • Removals are disclosed

    Available

    A removal is disclosed in the record, with who removed what and why. The disclosure is itself an entry in the firm's log, so it cannot be backdated, and missing entries that no disclosure covers still count against the log.

  • Retention ends with an attorney's act

    Collected bytes are not destroyed by default. A firm must enable a retention policy, and a licensed attorney approves the exact item set at execution. Active holds refuse destruction; disclosure comes first and record rows remain. Partial failures stay visible.

  • A prediction dated when it was made

    Available

    A prediction is recorded in the timestamped log when it is made. Whether it came before the outcome is then a comparison of two timestamps the firm did not write.

Your own AI tools, reading the record

  • Reads that carry their sources

    Available

    When your own AI tool reads the matter, each answer carries the record entries behind it, how far they were checked and the date of the data. Where statuses differ, it takes the weakest, and an answer with no sources reads as unknown.

  • Outside proposals wait for a person's approval

    Available

    A proposal from your tool joins BRON's own in the approval inbox and runs nothing until a person approves. A request to skip a check is removed, and the proposal says so. A matter holds at most 25 open proposals from outside tools.

  • What a key can reach

    Available

    A client-safe key sees only what privilege screening allows, whatever the request asks for. Only a firm administrator can approve an attorney key, and naming matters on a key can only narrow what its owner can reach.

What it reads from

  • Drafts and filings on the matter, with their versions
  • Citation check verdicts
  • The activity log and its timestamp proofs
  • Disclosed removals

Who can do what

  • Counsel chooses what leaves and retains the exact approved version. A recipient can independently check the supplied originals against their manifest without adopting the legal analysis.
  • An owner or admin exports the whole firm. Staff export a matter they can open.
  • Anyone with a digest can look it up on the verify page, with no account. The answer names no matter, party, title or file.
  • Someone holding a shared link can read the brief and the documents it cites. They cannot edit or export it, and the owner can revoke the link early.
  • A shared link is an access credential for its holder. A public digest lookup is only a fingerprint check; it grants no document or matter access.
  • A licensed attorney approves the exact collected-item set for destruction. Active holds refuse destruction; disclosure must be recorded first, and document, version, receipt and ledger rows remain.
  • Only a firm administrator can approve an attorney-class key for an outside tool. A client-safe key sees the matter with privileged material screened out.
  • An outside tool can read and propose. It cannot approve, send, sign or move money, and a matter holds at most 25 of its open proposals.

What it produces

  • Opposing counsel
  • A court or a clerk
  • The client, when the file is handed over
  • Your firm's own AI tools

Limits

  • A digest is evidence about one file at one time. It says nothing about what else the firm holds.
  • Source checks do not establish legal correctness. Recorded reliance is a review aid, not a claim to find every affected document.
  • A shared link is an access credential: keep it with its intended recipients. A public fingerprint lookup grants no access to the file or matter.
  • A new timestamp proof shows as pending until it is confirmed, usually within about a day.
  • The public calibration scoreboard is switched off. No prediction has been scored against a resolved outcome.

What BRON will not do

  • Say the record is whole.

    A digest shows that one file existed in that form at that time. It cannot show that nothing was withheld, and the lookup says so in its answer rather than in a footnote.

  • Serve a newer version through a link already sent.

    The link names the version it was made for and a digest of what it shows. If that version cannot be retrieved, the link refuses rather than showing another.

  • Count an unread source as verified.

    A source whose text was never opened is recorded as advisory, and the coverage counts show how many citations were advisory.

  • Report a log with missing entries as healthy.

    If a log now ends before a point its timestamp proof already recorded, the shortfall is counted. Missing entries that no disclosure accounts for decide the verdict.

  • Let an outside tool carry an approval.

    An approval is issued inside BRON when a person approves. A proposal from an outside tool cannot include one, and any it sends is removed.

  • Publish a calibration figure nobody can check.

    If the calibration log's verdict cannot be established, the public scoreboard shows unverified. Below ten resolved matters it shows no figure at all.

When something goes wrong

  • A byte match is not proof of completeness, legal correctness, receipt or reading of the underlying email, or admission at trial.
  • A link whose version cannot be retrieved refuses. It never shows a newer version instead.
  • A cited source that was never opened is recorded as advisory, not verified.
  • The archive carries available, export-cleared current document versions and listed record categories. It excludes other categories and is not the entire client file or proof that a transfer duty was fulfilled.
  • The preview names excluded categories and known omissions; the manifest records later file-read gaps. An empty omissions list does not include the excluded categories.
  • A new export's timestamp is pending or unavailable. Read the stated status; confirmation is a separate check.
  • Known reliance can guide review, but unrecorded reliance may exist. A source correction does not silently rewrite the approved work or change an existing shared version.
  • Destruction refuses active holds and unreadable safeguards. Partial failures are recorded, and bytes outside the application's reach are named rather than claimed destroyed.
  • If a log ends before its last entry anchored in time, the check reports the gap. Entries missing without a disclosure decide its verdict.
  • If an outside tool sends an override, BRON removes it and says so.
  • A matching file shows the bytes are the ones recorded. It does not show that nothing is missing.