Obligations you can query. Not re-read.
The auto-renewal buried on page 14 is invisible to every system that should act on it. Make it a property you can query.
The systems you already run, the objects your product declares, and the work your team gets back.
These marks name the kinds of system a source declaration reaches — a picture of the ecosystem, not a fixed menu, and nothing here implies a partnership.
Nothing lapses quietly. Nothing goes unrecorded.
Terms out of the PDF
Renewal date, notice period, liability cap become typed properties traceable to the file version they came from.
Extraction proposes, a person decides
A model suggests the value it read, but nothing becomes the record until a person confirms it.
Amendments that park for review
Changing a contractual term waits for a second reviewer, who sees the exact effects before releasing them.
What teams build. On day one.
Four places this work turns into declared objects, governed reads, and reviewed changes.
Renewal calendar
A Function lists every agreement that renews automatically in the next ninety days, each with its notice deadline and the clause behind it.
Notice windows
A Workflow waits until the notice period opens, then asks the owner to renew or exit. Silence leaves it open rather than lapsing.
Agreement intake
A signed contract enters as an immutable file version linked to its counterparty. The terms a model pulls out stay proposals until confirmed.
Counterparty exposure
One Function gathers every live agreement with a counterparty, its amendments, liability caps and open matters, instead of four people checking four systems.
How it runs. End to end.
The same path every product takes: connect what exists, declare what it means, then publish the reads and the changes.
- 01
Leave the executed originals alone
Your document store, contract system and finance tool keep the signed files, and nothing here writes back to them. Bijection copies them on a schedule you set, and each answer names the copy it read, so a clause amended this morning may not be in today’s list yet.
- 02
Declare what an agreement is here
Which terms you track, which dates matter, how an agreement links to its counterparty and its amendments. Written once in reviewed product source, not restated per template.
- 03
Put the gate where the risk is
An Action that changes a contractual fact can require review, and the reviewer cannot be whoever proposed it. Nothing takes effect while it waits, and the decision is appended with the change.
- 04
Let agents draft, never decide
An agent can find the clause and prepare the change through the same Functions a lawyer uses. Releasing it still crosses the reviewed Action, and the agent holds nothing the delegating lawyer does not.
Common questions.
No. Bijection is a domain-blind platform, and what makes it look like a contract system is a product declaration your team writes and reviews. It enforces the review rules you declare and records what happened. It does not interpret law, certify you against any framework, or make anything privileged.
No, and the design does not ask you to. Extraction proposes a value; a person confirms it through an Action, and the record shows who confirmed what against which file version. A term nobody has confirmed is reported as unconfirmed rather than presented as the record. A model can still misread a clause — what the platform guarantees is that its misreading never becomes the record on its own.
A mechanism, not a legal status. The application has no path to update or delete a fact once it is appended, and every fact carries its author, inputs and effects. Your database administrator remains inside the trust boundary, so this is not tamper-proof and we make no claim about how any court or regulator would treat it. Where that separation matters, the records can be exported to an independently administered archive.
Bring us a process.
We'll build it with you.
A business process, the systems it touches, and the rules it needs to follow.