Skip to content
BRON
← All of the product

06 · Deadlines

Anything may suggest. Almost nothing may mint.

A litigation date runs from a cited rule and a real trigger event. BRON computes the date, shows the derivation, and requires an attorney to confirm the trigger before anything reaches the calendar.

Register interest
MATTER 25001DEADLINE MINT
Opposing counsel served on the 4th. What is due?
RULEFed. R. Civ. P. 6(a)grounded
TRIGGERService, 2026-09-04review
DERIVATIONStored beside the dategrounded
FORUM NOBODY OWNSNamed refusal, no dateblocked

The trigger needs your confirmation before anything reaches the calendar.

The question in the room

“Will it ever invent a date?”

How it works

The mechanism, not the promise.

  • An asymmetry enforced by the build

    Around ten paths may suggest a date as a task. Exactly five paths across four allowlisted files may write one to the calendar, and a test fails the build if a sixth appears. There are no upsert calls anywhere in that seam.

  • The model extracts the trigger, never the date

    Rule identifiers must come from a closed list, a trigger must match an exact date shape, and every mint site round-trips the value through a real date so an impossible date is rejected rather than accepted.

  • An engine with named refusals

    Shipped

    Counting follows the federal rule for computing time, and a forum nobody owns gets a named refusal rather than a federal answer applied to a state matter.

    backend/src/lib/deadlines/frcp.ts

  • The derivation, stored beside the date

    Shipped

    The rule, the trigger and the count are kept with the date, so a date can be checked rather than trusted.

    backend/src/lib/deadlines/derivation.ts

  • A cascade that follows the trigger

    Shipped

    When the trigger moves, the dates that ran from it are re-derived as suggestions for confirmation.

    backend/src/lib/deadlines/cascade.ts

  • Judge and forum rules, asked once

    Shipped

    A forum's standing rules are captured once and reused, rather than re-asked per matter.

    backend/src/lib/deadlines/standingOrderOverlay.ts

Refusals

What it will not do, and why.

Let the model confirm its own date.
The create-deadline tool documents a confirmed parameter that is ignored. Confirmation is the attorney seeing the exact date before it lands.
Accept a client-supplied matter or author on a date.
Only a nine-key allowlist crosses into the write, so the matter, the creator and the identifier can never come from the caller.
Compute from today.
A date runs from service, entry of judgment or filing. Counting from the day someone opened the record produces a plausible date with no legal basis, which is the failure worth engineering against.

One record

Nothing here stands on its own.

What feeds it

  • Served and filed documents
  • The matter brain
  • Forum and judge rules

What it feeds

  • The calendar
  • The daily board
  • Workflow dependencies

Limits

What this does not establish.

  • Rules differ by court. A federal computation is not applied to a state matter.
  • An unowned forum produces a refusal that names itself rather than a computed date.

Check the work before you believe it.

Run a sample manifest in your own browser, or read where publication refuses for want of evidence.

Verify a record View calibration Register interest