Lab 18 · The audit · rebuilt on Untitled UI

The audit.

Every route in the five workspaces, every doctrine in the module documents, walked against the ten archetypes, twenty-four components and forty-three laws. Accounting got the deepest pass because it is the module the labs never gave a dedicated screen: thirty-six routes, an append-only journal, three-way matching, bank reconciliation, period close, segregation of duties and an AI agent that posts within a delegation.

The honest headline: the system holds, and the audit still earned its keep. It found three places where the system contradicts itself or the platform's own facts, one of which would have made accounting unbuildable as written, plus eight primitives the modules need that the labs never named, and a handful of places where the existing wireframes will have to change to comply.

The screens, rebuilt

Drawn fresh from the Untitled kit and the system’s ruled tokens, not restyled from the originals.

All nineteen statuses · the ruled pill, disposition on the ground, the clock in the dot
CustomerActiveProspectInactive
EnquiryNewQualifyingReady to quoteConvertedLostSpam
QuotationDraftSentApprovedAcceptedExpired
BookingIssuingConfirmedIn serviceCompletedCancelled

The reasoning, kept

01 / coverage

Where everything lands.

The strongest evidence came from accounting itself: its own design grammar, written independently, names five shapes, and they map onto the archetypes almost one to one. Two vocabularies arrived at the same building.

02 / the three contradictions

Where the system disagreed with itself, or with the facts.

These are the reason to run an audit. All three are cheap to fix now and expensive after adoption.

03 / additions

Eight primitives the modules need, and four laws.

None of these bends an existing rule. Most are the fill rule and the gate finding yet more work to do.

04 / stress

The hard scenarios, run on paper.

05 / adoption notes

Where the existing wireframes will change to comply.

Not gaps in the system; places where the built product predates it. Recorded so adoption is a checklist, not archaeology.

What this lab asked

  1. Kanban. Enquiries has a pipeline board today. Options: keep it as a lawful register view (cards obey row content rules, drag moves stage with the same logging as the action menu), or retire it and let the register's stage filter and the workspace stage bar carry the job. I lean to keeping it as a view, because a pipeline of open enquiries is genuinely spatial in a way a table is not, but it is the only card surface in the operator interface and that costs consistency.
  2. The three fixes in section 02. All three are corrections of the system's own inconsistencies rather than new design, so I have applied them to the specification and handbook. If any reads wrong, say so and it reverts.
The original document, in its own chrome and drawings, is kept unedited: open the original.
Tripbooks Design SystemBuilt on Untitled UI · Inter for language, IBM Plex Mono for every figureLight and dark from the same tokens