Two palettes, both real
The console's tokens (ago-console/src/design/tokens.css) are the
canonical set — the file's own header calls it "the single source" and traces every value
back to an earlier version of the landing page. The landing page has since been redesigned
around its own, narrower palette (its own stylesheet calls this "a second stylesheet...
this page's redesign changes tokens, type and component shapes wholesale"). Both are shown
below, honestly, rather than picking one and pretending the other doesn't exist. The
type page documents the identical shape of drift for the
font stacks.
Console tokens — brand & accent
"the console spends [brand] on exactly one primary action per screen, the active navigation item, links, and the focus ring" — tokens.css's own usage-restraint comment, contrasted there with the landing page, which "paints whole sections" in it. Light values shown; the file also carries a full measured dark palette for each.
Console tokens — status
Danger and warning are kept in the "same darkness band" on purpose, per tokens.css, "so it reads as a sibling of the palette rather than a bootstrap red." Warning is deliberately not danger-toned: "the whole point is that this must not read as a sibling of danger" (25-83's own decision, quoted in tokens.css).
Console tokens — ink & paper
Every pair here "was measured (WCAG 2.1 relative luminance) rather than eyeballed" — tokens.css records the ratio inline for each. Text pairs clear 4.5:1.
Landing's own palette
The front page's current design system (ago-landing/styles.css),
dark-first: "the page was designed as a control panel and reads as one." Not the same values
as the console tokens above — this is the redesign the console's own file predates.