Put the explorer on the shared design system and the estate ladder - #574
Merged
Conversation
The primary was the same value as another token in two of these files: action in atrib-internal, ink in atrib-cloud. A product whose pitch is that a decision can be checked cannot spend its brand colour on one of the outcomes, and a product whose primary is its body text has none. Cobalt is the primary. Literata, Libre Franklin and IoskeleyMono replace Inter and General Sans, all SIL OFL and all served from our own origin. Frontmatter values are left as written. They are a machine-readable contract and rewriting them is a separate decision.
The mark linked to the explorer's own root, so a reader who followed the evidence link from the site had no way back. It goes to atrib.dev now, from here as from everywhere. The estate ladder joins the header and the surface map joins the footer, both generated from atrib-web/lib/surfaces.json by scripts/render-nav.mjs so they cannot drift from the other surfaces. The explorer's own sections move to their own row: mixing "where am I in the estate" with "where am I in this page" is what made three surfaces read as three products. The canvas moves from neutral #0a0a0a to the column's own #050914. Amber measures 9.07 there against 9.02 before, and every neutral solves contrast(x, floor) equal to contrast(old, #0a0a0a) at hue 220 to 232, so each step survives to two decimals. Cobalt joins as the primary; the explorer had none, which is why amber was carrying headings as well as evidence. Status colours were Tailwind's default 400 ramp, a palette belonging to no part of this product. Four now come from the design system. warn is deliberately left: our review colour is hue 35 and the evidence mark is hue 32, so lifting it to this ground makes them the same colour, and choosing what "needs a human" looks like at depth is a decision rather than a mapping. The new-row highlight was a wash applied twice, on the row and again on the cell. Every chip here is a colour on a 12% tint of itself, which leaves the dimmest at 4.56, so a wash underneath pushed all six chip colours under 4.5 and the worst to 2.00. It is a rail now, in the gutter rather than behind the text. Two event-type chips read 3.76 and 2.50 against their own tint at 11px and were lifted at their own hue. The categorical scheme is unchanged: those hues encode protocol event types per D056 and D058, not brand. Measured after, compositing translucent layers: zero contrast failures across 627 elements.
protocol was generated as absent because protocol.atrib.dev has no DNS record yet, but the protocol website is live at atrib.dev and always was. The explorer now links to it, and its home link points at the bay page rather than at the protocol site.
The hostname exists now. Regenerated from atrib-web/lib/surfaces.json.
…ur-and-type-20260728
textleaks flagged the nagala.workers.dev hostname as a cross-project codename leak in a public repo, correctly. Phase 0 of the consolidation already names this: the proof is fine, its address is wrong. It returns to every nav when it answers on an atrib hostname.
atrib is the applied product and atrib protocol is the open substrate, so the separate not-public 'operating graph' surface is gone and the two blurbs name the layers correctly. Generated from atrib-web/lib/surfaces.json.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The explorer was one of three surfaces running three different navigation
vocabularies, and its mark linked to its own root, so a reader who followed the
evidence link from the website had no way back to the claim.
Navigation
atrib.dev, from here as from every other surface.are generated from
atrib-web/lib/surfaces.jsonbyscripts/render-nav.mjs,so they cannot drift from the other surfaces.
estate" with "where am I in this page" is what made three surfaces read as
three products.
Colour
The canvas moves from neutral
#0a0a0ato the water column's own#050914, sothe instrument sits on the same hue axis as the rest of the brand. Amber measures
9.07 there against 9.02 before. Every neutral solves
contrast(x, floor) == contrast(old, #0a0a0a)at hue 220 to 232, so each stepsurvives to two decimals. Cobalt joins as the primary; the explorer had none,
which is why amber was carrying headings as well as evidence.
Status colours were Tailwind's default 400 ramp. Four now come from the design
system.
warnis deliberately unchanged: our review colour is hue 35 and theevidence mark is hue 32, so lifting it to this ground makes them the same colour.
Choosing what "needs a human" looks like at depth is a decision, not a mapping.
Two contrast defects, both pre-existing
The new-row highlight was a wash applied twice, on the row and again on the cell.
Every chip here is a colour on a 12% tint of itself, which leaves the dimmest at
4.56, so a wash underneath pushed all six chip colours under 4.5 and the worst
to 2.00. It is a rail now, in the gutter rather than behind the text.
Two event-type chips read 3.76 and 2.50 against their own tint at 11px and were
lifted at their own hue. The categorical scheme is unchanged: those hues encode
protocol event types per D056 and D058, not brand.
Verification
Measured in-browser after, compositing translucent layers rather than stopping
at the first one: zero contrast failures across 627 elements. HTML parses
balanced. The active-route highlight was rescoped to
nav a[data-route]becausethe local nav is no longer inside
<header>.Canonical system:
atrib-web/designs/fable5-authored-territories-20260721/DESIGN-SYSTEM.md