08 — UX mockups

Summary

The v0.33.61 register-UI brief settles the primitive — a badge on every edge, carrying who can verify it, by what method, at what cost, when it was last checked and what the answer was. This document draws the screens: the agent page that must answer six questions without a reader leaving it, one badge expanded into its transcript (including what the check did not establish), the register index reporting its own unverifiable fraction, the mandate composer showing excess authority before the mandate is signed, a policy page that says “0 rows” and “detects nothing” on the same screen, the blind-ack enrolment view, the verifier’s answer and its refusal, the empty and failure states, and the CLI that reaches every one of the same answers.

Key concepts

• The badge, with five result states — confirmed, denied, unknown, unreachable, not checked — and the last three are not the same
• Verifiable by nobody — a rendered fact about the world, never a blank — C10’s primitive arriving as pixels
• Excess authority, before signing — the composer shows grant minus mandate at issue time, not six weeks later

Key ideas

• Seven strings are load-bearing: each is the only place a reader learns something the rest of the screen cannot tell them.
• No trust score, no page-level tick, no live capability ever rendered — three deliberate absences.
• The CLI mirrors every screen, because if the page is the only route to the answer the design has acquired a dependency it says it does not have.

Read the document