CAPABILITY 09 / 30

A human decision outranks the data

When a person overrules a source, the system remembers who, why, and until when.

IN PRODUCTION

This runs in client systems today. The sample below was regenerated for a fictional company.

A system that always trusts its data will confidently repeat a number somebody already overruled. The fix is a decision record: it wins on every future read, it carries the person and the reason, and when the source underneath it changes it resurfaces for review instead of quietly disappearing.

TRY IT / RUNS IN YOUR BROWSER

Use it here.

The mechanism is the production one. The company, the catalogue, and every figure are fictional.

Loading the decision register.

THE OUTPUT / GENERATED FOR APEX INSTRUMENTS

What comes out.

JSON

Three sources a system would read fromData · A price list, a service levels table, and a product spec sheet, each with a revision, an effective date, an issue date, an owner, and a fingerprint. Ten fields across the three. Each source also carries a reissue: the revision it would move to, its new fingerprint, and the values that move. The seven precedence rules the resolver runs are published here too, so the rule set is data rather than code.Open the file ↗

JSON

The Apex decision register, ten recordsData · Each record carries the field it governs, the value the source said when it was written, the value a person decided, the reason in one sentence, who decided and their role, the date, a review date and an optional expiry, a scope of global, one partner, or one region, a filed status, and the named reviewer. Six active, one expired, one needs review because its source moved after the decision, and two superseded, which are kept on file so the history of a figure stays readable.Open the file ↗

THE MECHANISM / SHOW THE SHAPE, NOT THE SOURCE

How it works.

What a skill is

01Read the source
Every field has a source value with an effective date and a fingerprint.
02Check for a decision
A decision record on that field outranks the source.
03Answer with the record
The answer carries who decided, why, and when it is due for review.
04Watch the source
When the source changes under a decision, the record flips to needs review rather than losing.
05Respect the edges
A scoped decision does not leak beyond its scope, and an expired one stops applying on its date.

WHAT IT READS

The source records a system reads from
A decision record per overruled field
A scope and a review date for each decision

WHAT IT CHECKS BEFORE IT SHIPS

A governed field never returns the source value silently
Every decision names a person, a reason, and a date
A partner-scoped decision cannot reach a general document
An expired decision stops applying without anyone remembering to remove it

In production: a decision record file governs the fields where a person has overruled the data in one company system.

The mechanism runs inside client systems. Everything on this page was regenerated for Apex Instruments, a company that does not exist. Client names, source files, and internal wording stay private.

What it produces What is being built next