NASD OTC Securities ExchangeA Self-Regulatory Organisation, registered with and
regulated by the Securities and Exchange Commission, Nigeria
NASD NEXT · GATE SERIES · 04 · THE LAWS

The three build laws

v2 · 22 Jul 2026 · read ledger · honest state · lawful fallback · companions: 01, 02, 03
THE LOGIC WE ARE AIMING FOR

Three laws, one constitution: record every touch, tell the truth about every state, and under stress shed speed, never legality. They interlock; adopt all three or the gap leaks through the one you dropped.

Below: the adoption sequence (which law first and why), the laws translated to four altitudes with the reviewer's question at each, and the price of each law stated up front.
HOW TO THINK ABOUT IMPLEMENTING THEM

The adoption sequence

Laws that arrive as announcements get ignored. These arrive as an order of operations, a price tag, and a set of questions wired into review.
Adopt Law 2 firstHonest state is the cheapest visible win: enumerate the real states, write the copy beside the code, ban the catch-alls. Users and Exco feel it in weeks.WHY THIS ORDER · it needs no new infrastructure and builds the habit the other laws depend on
Lay Law 1 as substrateThe read ledger ships with the object store (Build Book stage 1), then extends to the write ledger for obligations: assignments and submissions as recorded events.WHY THIS ORDER · retrofitting provenance is archaeology; it must ride the first schema
Rehearse Law 3 into existenceName every automated path's lawful fallback, build it, drill it quarterly. An unexercised fallback is a Law 2 violation waiting to happen.WHY THIS ORDER · a fallback becomes real the first time it runs with real users, not when it is documented
Wire the questions into reviewThe altitude questions below go into the design-review and PR templates verbatim. Compliance stops being a meeting and becomes a checkbox with teeth.WHY THIS ORDER · enforcement at the point of decision, exactly as grants enforce at the endpoint
THE LAWS, BY ALTITUDE

The laws, stated by altitude

LAW 1 · THE READ LEDGER

Every access is an event on the record it accessed

Enforcement lives at the endpoint, never in the UI or in policy; a grant not checked at the point of service is a wish. The ledger is symmetric: platform and insider reads land beside external ones.

ENDPOINTNo valid grant, no bytes; reads write. Ask: show the code path where an unauthorised read is refused, and the event the refusal writes.
PRODUCT“Who has seen my data” is a user-facing query. Ask: where does the user see their read ledger?
ORGANISATIONObligations are ledgered writes; ownership is never a memory dispute. Ask: when this was assigned, what recorded it?
GROUPOne convention, one answer to every auditor. Ask: is this build adopting the convention or inventing a private one?
LAW 2 · HONEST STATE

Degraded is allowed; lying about it is not

No false errors, no optimistic countdowns, no dead ends dressed as waiting screens. Every blocked state names its reason and next action.

ENDPOINTThe real state machine exists in code with versioned copy. Ask: enumerate the states; show the copy for the worst one.
PRODUCTReal queue times; stale reads stamped stale. Ask: when this number is wrong, how does the user know?
ORGANISATIONStatus is glanceable: owner, blocker, next action, on the record. Ask: could a third party reconstruct this workstream without interviewing anyone?
GROUPIncidents disclosed in the product's own honest voice. Ask: does the comms plan survive being screenshotted?
LAW 3 · LAWFUL FALLBACK

Under stress, shed speed, never legality

The degraded mode is the slower lawful path, never the faster unlawful one. The epistemic governor compiled into architecture: permission contracts as conditions degrade.

ENDPOINTEvery automated path has a named, built, drilled fallback. Ask: when did we last run it with real users?
PRODUCTDegraded flows say they are slower and why. Ask: what does the user see the day the fast path is off?
ORGANISATIONNo metric tempts anyone to bend a rule. Ask: which target would, and what protects the person who refuses?
GROUPWork with the regulator's grain; request changes openly. Ask: is this design with the grain or against it?
CONSTRAINTS

Interlock and price

INTERLOCK

All three or none

Law 3 is only safe because Law 2 tells the truth about the slower path; Law 2 is only auditable because Law 1 recorded what happened. Keep two and the gap leaks through the one you dropped.

PRICE

Priced at adoption, not discovered in sprint three

LAW 1Write amplification on every access; bounded by batching and tiering ledger-worthy reads. Never free.
LAW 2The real state machine plus copy maintained as code.
LAW 3The lawful slow path built and rehearsed, on the calendar.

One breath: record every touch, tell the truth about every state, and when things break, get slower, never get illegal.