MEtronome · design lab · 2026-08-26 · B2 · 1.1+ arc · 1.0 scope untouched

Accent Lab
Six families, one field

The brief was “brighter, more premium, not AI-generated ember.” R4 already established that amber is not the named 2026 AI tell — indigo/violet and neon-on-dark glow are — and that the real tell is structural: a saturated glow on a near-black field, regardless of hue. So this lab does not ask “which hue is less AI-looking.” It asks the only question a mockup can actually answer: put six accent families on the identical bright screen, run the identical beat, and see which one is still alive.

Every panel below shares one field (Studio #F5F6F8), one layout, one beat clock, and one generated markup template. The only difference between any two phones on this page is the accent token triple. Ratios are computed WCAG 2.1, worst-case across Studio’s three grounds, by a calculator first forced to reproduce D1’s eleven banked ratios — and then, as an independent check, all eighteen of R4 §3’s anchors, which it reproduced exactly.

01

The honest A/B

Seven screens, one clock. Ember is the control — it is literally D1’s Studio panel (palette-lab.html:559-641), unchanged, so the comparison is against the real proposal rather than a re-tuned strawman. Arm the sound if you want the beat in your ears; the ring below is the gesture iOS Safari requires, and nothing on this page makes noise before you hit it.

ARMSOUND + BEAT
audio: not armed
beat: stopped
PICK YOUR COLOR H217° — lightness is solved, not picked. The eighth phone in the deck is yours.

GREYSCALE strips hue and leaves luminance structure — if a family only works in colour, it fails here. DOSAGE X-RAY hairlines every element spending accent chroma, because R4 §4.1 is explicit that dosage, not hue, is the machine-generated tell. CONSOLE swaps the field to graphite and flips the armed direction from burn to glow; §04 is what that switch costs each family.

02

The armed rule, per family

D1 §2 states the law in three parts: armed is always the largest luminance step from the field (A); #F0A040 can never clear 3:1 above field luminance 0.1135 (B); above that ceiling the armed dot becomes a burn core with the sacred hex kept as the bloom (C). Swapping the accent family does not repeal any of it — it just replaces which hex is sacred. Each family here has a flare: its own signature chroma, the analogue of #F0A040, and every flare has its own computed ceiling.

FINDING 1Every family hits the same ceiling. None of them clears the bright field.

Studio’s field sits at L = 0.9210. The highest flare ceiling in the whole set is Instrument Cyan’s L ≤ 0.1151 — a hair above amber’s own 0.1135, and still eight times too dark to matter. On a bright field no saturated accent can be the armed core at 3:1, for the same physics reason amber cannot. Law C is not an amber workaround. It is what a bright field does to any hue. That is worth knowing before the owner picks: the burn treatment is not a compromise forced by the incumbent colour, it is the bright field’s native armed grammar, and it stays whatever he chooses.

FINDING 2On a bright field the glow stops being the mechanism — and that is the anti-AI win

R4 §1 names unmotivated glow as the most literal AI signature there is. Compute what the bloom actually does on Studio and the argument settles itself. A bloom is a translucent flare over the ground; composited at the app’s own 0.85 alpha over #F5F6F8, here is what each family’s halo is worth as contrast:

FamilyFlareFlare L Bloom @ .85 over #F5F6F8Ratio vs fieldReads as
Ember (control)#F0A0400.4404#F1AD5C1.79a tint
Instrument Cyan#24C3DB0.4452#43CBDF1.79a tint
Jewel Pine#28C3680.4048#47CB7E1.92a tint
Cognac#D4975E0.3694#D9A5752.03a tint
Oxblood#FF63630.3108#FE79792.36a soft mark
Restrained Indigo#7170FF0.2232#8584FE2.89a real mark
Signal Red#D520260.1532#DA40464.04a hard mark

Five of seven halos land between 1.79 and 2.36 — below the 3:1 graphics floor, i.e. decoration by measurement. On the bright field the thing that carries “alive” is the burn core, not the halo. Which is the same as saying: the bright field forces the exact discipline R4 §4.2 says separates designed from generated — glow that is load-bearing, or no glow at all. The owner’s field preference already did most of the anti-AI work before a hue was chosen.

FINDING 3“Isn’t a bright field also the current template look?” — no, and the number says which side of neutral you are on

This is the obvious objection to FINDING 2 and it deserves a measured answer, because R4 names two field tells, not one. The first is permanent dark mode (R4-accent-trends.md:53). The second is the 2026 backlash-default (R4-accent-trends.md:54): a cream/beige ground — #faf8f5, #f5f1e8 — under forest-green or sage, which became a cliché precisely because every piece of anti-slop advice converged on the same escape route. Leaving dark mode is not automatically leaving the template; it can be a lane change into the other template.

Studio is not that ground, and the separation is not a matter of taste — it is the sign of b* in CIELAB. Cream is warm: b* is positive. Studio is a cool near-white: b* is negative on all three of its grounds. They sit on opposite sides of the neutral axis.

GroundHexL*a* b*Side of neutralWhat it is
Backlash cream#faf8f597.7+0.15+1.66WARMthe named 2026 cliché
Backlash beige#f5f1e895.2−0.20+4.80WARMthe named 2026 cliché
Studio · primary#F5F6F896.9+0.03−1.09COOLpaper under daylight
Studio · elevated#EFF1F495.1−0.12−1.69COOL—
Studio · secondary#E8EAEE92.7+0.06−2.18COOL—

Same lightness band — L* 92.7–97.7 for every row — and opposite chroma sign. The gap is small in absolute terms (2.75 b* units to the cream, 5.89 to the beige) but it is the difference between “warm paper” and “cold paper”, which is the whole read of the surface. And the accent seals it: the backlash-default pairs its cream with sage or forest green. Of the six families in §03, the one that would land MEtronome inside that cliché is Jewel Pine — and §07 already excludes it, for an unrelated reason (it sits 6° from success, §05). Two independent disqualifications is not a coincidence worth leaning on, so take this as the second one and not the first: a family can hold every ratio it needs and still fail the originality test. Pine holds all of them, on both fields. It is still the one hue on the page that a 2026 viewer has been primed to read as the tasteful default.

[unverified] The b* figures are computed here from sRGB under D65 with the standard CIE matrix; the two cliché hexes are R4’s own, quoted from the source, not sampled from a live product. The claim that cool near-white reads as un-templated to a human eye is a design judgement resting on the sign, not a measured perceptual result.

FLAGGEDOne number in the prior lab is mislabelled (no decision changes)

palette-lab.html:626 reports Studio’s dotNorm #C3C8D0 as 1.55 in a column headed “worst of P/S/E”. Recomputed: 1.55 on bgPrimary, 1.49 on bgElevated, 1.40 on bgSecondary. The value is correct for the F6 visibility floor, which the audit defines on bgPrimary (palette-accessibility-audit.md §7, “1.52 / 1.99 on bgPrimary”) — it is the column header that is wrong, not the token. Nothing here or in D1 turns on it. Recorded because a lab that quietly reproduces a neighbour’s label error is worth less than one that says so.

03

Six families + the control

One line of character each — what the colour is, not what it is selling. armed / resting / dimtext are R4 §3’s hexes, independently recomputed here and matching to the second decimal. Everything else is derived on this page by bisection against a stated target. ARM-STEP S = armed ÷ resting; floor 1.30 (SYNTHESIS.md:129).

04

The matrix has holes

Accent-as-a-dimension implies every (field × accent) pair is buildable. It is not. On a dark field the armed core must glow, and the chain dimText ≥ 4.5 · dimText < resting · armed ÷ resting ≥ 1.30 forces armed ≥ ~5.85. Measured against Console’s worst ground — the elevated #232831, L = 0.0210, not the base #1C2027, L = 0.0143 — three families cannot get there with their own flare. (Light-on-dark: the worst case is the brightest ground, per the method note at the head of this file. On #1C2027 every figure below reads 0.6–0.7 higher and Oxblood would scrape past; the column is stated at the ground the app will actually elevate a card onto.)

FamilyFlareon CONSOLEVerdict Armed core it would needLiftWhat the lift costs
Ember (control)#F0A0406.91HOLDS#F0A040 — sacred, intact0—
Instrument Cyan#24C3DB6.98HOLDS#24C3DB0—
Jewel Pine#28C3686.41HOLDS#28C3680—
Cognac#D4975E5.91HAIRLINE#D4975E, resting pinned 4.50–4.550a 0.05-wide legal window — one HSL point breaks it
Oxblood#FF63635.08FAILS#EA9BAD+7oxblood becomes dusty rose — the character is the loss
Restrained Indigo#7170FF3.85FAILS#B4AAE2+6lavender — and lavender is the named cliché
Signal Red#D520262.86FAILS#F0999C+29salmon. Braun’s Signal Red does not survive it

FINDING 4The inverse of amber — and it points at the owner’s own preference

Amber’s whole problem, per D1 §2 and R4 §2, is that it is too bright to be armed on a light field. The three families with the most headroom on Studio — Oxblood 12.72, Indigo 12.99, Signal Red 11.53 — have the least on graphite, for the mirrored reason: they are too dark to glow. They are bright-field-only accents. That is not a defect to engineer around; it is a constraint that happens to point the same way the owner already went. If he wants a genuinely non-amber accent, Studio is not a preference sitting next to it — Studio is the field where it is possible. The counterpart is equally firm: the accent dimension must be able to say “illegal on this field” in the type system, not in a comment (§06).

05

Semantic collision

Theme.swift:66-76 holds success and destructive as absolutes — a green that means connected and a red that means delete. They are field-owned, not accent-owned, so they do not move when the accent does. Three families walk straight into one of them. Studio’s values: success #2E8B57 (H146°), destructive #C0362B (H4°). ΔH is measured from each family’s RESTING hex — the swatch shown — not from the nominal hue it was derived at, which for several families differs by a few degrees once the token is quantised to 8-bit sRGB.

FamilyRestingHΔH vs successΔH vs destructiveReadIf chosen
Ember (control)#91490F27°120°22°nearships today; separated by shape + placement, not hue
Instrument Cyan#296B76189°42°176°clearest of the sixno action
Jewel Pine#2E7345140°6°136°collides — successthe connected-peer dot and the accent become one colour. Re-hue success, or drop B.
Oxblood#8C2E3E350°157°15°collides — destructivedelete-red and the beat accent share a family
Cognac#7A523028°119°23°nearsame exposure as Ember, no better
Restrained Indigo#5B52A3247°100°118°clear on boththe only family that clears both outright
Signal Red#B23A343°144°2°collides hard“the only armed colour” and “destroy this” become indistinguishable

R4 §3F already flagged this for Signal Red and proposed pulling the hue to 358° to dodge it. Measured on the resting token that actually ships, the dodge is 2° — it does not clear anything; the quantised token lands at H3°, one degree off destructive’s H4°. This is the strongest argument against F that exists, and it is arithmetic rather than taste: the family with the best design-history case (Braun, one functional accent, nothing decorative) is the family whose meaning is already taken inside this app.

06

The anti-AI test

THE TESTWould this colour survive being screen-printed on a hardware faceplate?

A screen accent costs nothing — you type six hex digits and the compiler agrees. A faceplate colour costs a paint run, a minimum order, and a decade of the thing sitting on a desk in daylight looking like whatever it looked like. That asymmetry is exactly what R4 §4.3 identified as the fix: a chosen colour tied to a specific reference, not a statistically safe default. So the test is a proxy for deliberateness, and it is falsifiable — either a real manufacturer has committed this colour to physical goods in this category, or nobody has.

It rules out the two things that make generated colour look generated. A hue that only exists because it glows well on black fails it (no faceplate glows). A hue picked because it is inoffensive fails it too (nobody tools up for inoffensive). What passes is a colour somebody paid to be sure about.

FamilyFaceplate testThe physical precedentR4 risk
Ember (control)PASSESTeenage Engineering’s orange-on-aluminium, itself lifted from industrial safety-equipment convention (R4 [^7])—
Instrument CyanPASSESInstrument-panel convention; RME ships a first-class Light Theme in this exact product category (R4 [^3])2
Jewel PinePASSESRolex, Chopard, IWC 2026 dials; Porsche “Python Green” trim (R4 [^4][^5]) — paid-for, physical, this year2
OxbloodPASSES — strongestBreitling + Seiko 2026 dials, and Raycast Red as the software descendant (R4 [^4][^6])1
CognacUNPROVENR4 §3D is explicit: no named citation, [unverified as a 2026 trend]. It is a safer default, which is what the test is built to catch.4
Restrained IndigoFAILSLinear is software-only (R4 [^8]); no hardware precedent surfaced. This hue exists on screens because screens are cheap.4
Signal RedPASSES — deepestBraun Signal Red on physical operational controls, sixty years of it (R4 [^9]). Passes the test and then loses on §05.2

[unverified] The faceplate test is this lab’s own framing, not a sourced methodology. The precedents in the right-hand column are R4’s citations; the pass/fail column is judgement applied to them. It is offered as a decision aid the owner can reject, not as a measurement — unlike every ratio on this page, which is not a judgement at all.

07

Where this lands (owner’s call)

Not this lab’s ruling to make — house convention puts that with the owner (SYNTHESIS.md:255). What the lab can do is say what is now decided by measurement rather than taste, so the taste question gets smaller:

1 · The burn treatment is settled, whatever he picks. No family clears the bright field’s armed ceiling (§02). Burn core + flare bloom is the bright field’s grammar, not amber’s workaround. And the field itself already clears both of R4’s field tells: it is not dark, and its b* is negative on all three grounds, putting it on the opposite side of neutral from the cream/beige backlash-default (§02, FINDING 3).

2 · Three families are Studio-only. Oxblood, Indigo and Signal Red cannot glow on a dark field without losing the character they were chosen for (§04). If the owner wants one of those, the theme menu owes the user a bright field, and the code owes the compiler a way to say so.

3 · Two families are already spoken for inside the app. Jewel Pine sits 6° from success; Signal Red sits 2° from destructive (§05). Both are shippable only by re-huing a semantic token — a bigger change than an accent swap, and one that touches screens outside this arc.

4 · That leaves Instrument Cyan and Oxblood as the two clean answers — which is exactly where R4 §6 landed from evidence alone, now with the numbers and the collisions agreeing. Cyan is the only family that clears every gate on both fields. Oxblood is the strongest character and the best faceplate case, at the price of being Studio-only and 15° from destructive.

5 · Cognac still does not answer the brief. It is 4° of hue from the incumbent, has no sourced precedent, and its Console window is 0.05 wide. It is on this page as the honest control for “maybe he meant saturation, not hue” — and if that is what he meant, the answer is not Cognac, it is Ember with the glow discipline of §02 applied.

What this lab has not done: no device pass, no OLED behaviour, no daylight-readability test, and no colour-vision-deficiency simulation — the greyscale toggle is a luminance check, not a CVD check, and deuteranopia in particular would treat Jewel Pine and Signal Red very differently from how this page shows them. Nothing here has been seen on glass.