Every decision,
kept.

A Decision Record is the call itself, kept as a durable object: the question, the options you did not pick, the evidence, the sign-offs, and the result. Typed, content-addressed, sealed when saved. The one thing every other tool helps you make, and none of them keeps.

Talk to us See inside a Record

New here? What is a decision system of record

Sealed

DR-2026-0142 Sealed 2026-06-18 · 14:22 UTC

If we reduce the vendor base by 10%, which programs do we protect?

Decision Evidence Sign-offs Replay

Options

Consolidate T3 contractors in Vendor Group C Selected

Reduce by headcount across all tiers Rejected

Defer until Q3 cost-center data is complete Rejected

Confidence

High on direction · Medium on precision0.74

Gating risk: cost-center field missing on 99.5% of active rows. Carried into the confidence band rather than ignored.

hash 7f3a · c91d · 8e20 · b44f Content-addressed

An enterprise keeps everything except the decision.

Every invoice, every contract, every employee record is filed in a system built to keep it. The decision those things were gathered to make is the one thing that is not. It happens in a meeting, a thread, and a slide, and then it is gone: not the question as it was framed, not the options that lost, not the reason they lost. AI made that sharper, not better. A model generates a recommendation in seconds, so the recommendation is cheap. What is scarce is the kept, accountable record of the call.

Every part of a Record is kept for a reason.

The question, the options including the ones not picked, the evidence, the sign-offs, the result, and how sure the call was. Select any part to read why it is there.

DR-2026-0142 Sealed

Question If we reduce the vendor base by 10%, which programs do we protect?

Options

Consolidate T3 contractors in Group C Reduce by headcount across all tiers Defer until Q3 cost-center data is complete

Evidence

workforce_export_q2.csv continuity_matrix.xlsx rubric_v7

Confidence

High on direction · Medium on precision0.74

Cost-center field missing on 99.5% of active rows. Carried into the band.

Sign-offs

PRProcurement FNFinance LGLegal

Result Consolidate T3 contractors in Group C. Protect Group A coverage. Sealed 2026-06-18 · 14:22 UTC.

hash 7f3a · c91d · 8e20 · b44f Content-addressed

The address

A Decision Record is content-addressed: its identity is its contents. Change one field and it becomes a different record with a different address, so the original stays complete and self-describing. The hash is how you check that what you opened is what was saved.

Content-addressed · self-describing

The question, as framed

Most calls are won or lost in how the question is framed, not in the answer. The Record keeps the framing, in the words the decision was actually made in, so a year later you can see what was being asked and not just what was concluded.

Framing is kept, not just the answer

The options, including the rejected

This is what a dashboard throws away. The options that lost, sitting next to the one that won, with the reason each was rejected. It is the first thing audit asks for and the last thing anyone wrote down. The Record keeps the road not taken.

The road not taken, kept

The evidence

What the call was actually based on, linked and addressable. A year later you are reading the inputs as they stood when the decision was made, not reconstructing them from memory or hoping the file still exists.

The inputs, as they stood

The confidence band, calibrated

High on direction, medium on precision because of a known data gap, is more defensible than a single confident number that hides the gap. The Record carries what the decision did not know, on purpose. Calibration is where a decision separates from a calculation.

It carries what it does not know

The sign-offs

Who owns the call, and when they signed. Accountability is a field in the Record, not an afterthought in someone's inbox. When the question comes back, the names are already attached to the decision they approved.

Accountability is a field

The result, sealed

The moment it is saved, the Record is sealed and content-addressed. It cannot be quietly edited later. A correction is a new record that supersedes this one, on the record, so the history of the call is append-only and never rewritten.

Sealed · superseded, never rewritten

Every part of a Decision Record, and why it is kept. Select a row to read it.

It keeps the options you didn't choose.

A dashboard keeps the answer. A chat keeps the transcript until you close the tab. Neither keeps the option you rejected, the reason you rejected it, or the dissent that turns out, a year later, to have been right. Switch the view and watch what survives.

The answer it produced

The chart or the ranking

The question, as you framed it

The options you rejected

Why you rejected them

The dissent in the room

The data gap behind the confidence

Who signed, and when

Reconstructable a year later

A dashboard or a chat keeps the answer. The decision behind it is gone.

Same call, two ways of keeping it. Only one keeps the decision.

Sealed when saved, reconstructable for years.

The moment a call is signed, the Record is sealed and content-addressed: its identity is its contents, so what you open is provably what was saved. A correction does not edit it. A correction is a new record that supersedes it, so the history of a decision is append-only and never quietly rewritten.

We are deliberate about what sealed means, because a system of record that overclaims is worse than none. Today it means three things you can check: the Record is complete, it is content-addressed, and it is self-describing. Full tamper-evidence against a determined insider needs more: an external trust anchor outside your own tenant, and deterministic replay from pinned inputs. We are building toward both, and we will claim them when they hold, not before.

Capture

The question, the options including the rejected, the evidence, the sign-offs, the result, the confidence.

Draft

Seal

Sealed when saved. Content-addressed and self-describing. It is not edited; it is superseded.

Sealed

Reconstruct

Pull it up months later and read the decision as it stood, under the information available then.

Reconstructable

When finance, audit, a board, or a regulator asks why a call was made, you open the Record and read the decision as it stood: the question as framed, the options as weighed, the evidence as it was then, the people who signed. This is reconstruction, not recollection. You are not asking someone to remember it. You are reading it.

One record links into the graph.

A Decision Record never sits alone. The moment it is sealed it links into the Decision Graph: the records it built on, the one it supersedes, the ones it had to reconcile. The object is the Record. The asset that compounds is the Graph.

The Decision Graph

Records reference, supersede, and reconcile one another into an append-only memory of how the enterprise decides. Owned, portable, and queryable across time.

The owned, compounding memory

How the platform works

The Decision Intelligence Core turns a question into a sealed Record and links it into the Graph. Four layers, wrapped by governance and learning, running in your environment.

The Core, the architecture, deployment

See a record on your decisions.

Watch Nexonomy capture, seal, and reconstruct one of your decisions, in your environment, watch-only first.

Talk to us See the Decision Graph

Every decision,kept.