Ship the platform as a living surface, not a release. Feature-flag everything; let production teams roll out capabilities to fleets in cohorts without redeploying the console.

Workstations run 10–14h shifts under variable lighting. Type stays at 16px minimum; primary actions clear AAA contrast on every surface; error states never rely on hue alone.

Every OTA action — operator, target VIN range, package hash, timestamp — is logged and exportable. The interface surfaces this trail in-context, not in a separate compliance tool.

Yes — typically as a 12–16 week engagement with embedded engineering pairing. I don't ship throwaway redesigns; the system has to outlive my involvement.

Two weeks for a discovery sprint — research, audit, a short written direction. Anything shorter doesn't leave room to disagree with the brief, which is usually where the work is.

Remote-first, with on-site weeks for kickoff and major milestones. I'm based in Milan and travel comfortably across EU.

MINOR. No token changed. Cursor started reading agent skills in January and the IDE download never caught up, so it shipped the constraints without the procedure. Fixing that led to three pieces of drift in this repo that every gate reported green: the version line the spec calls canonical, a download button named after a file deleted three releases ago, and a debt mechanism whose deadlines never arrived.

Added

• The agent skill reaches the IDE — since Cursor 2.4 the Agent Skills standard is a first-class input, read from .cursor/skills/, .agents/skills/ and, for compatibility, .claude/skills/ and .codex/skills/. amaca-ide.zip now carries amaca-frontend unpacked under .agents/skills/amaca-frontend/ — the vendor-neutral path, so one folder serves Cursor and Codex alike. The spec is not duplicated inside it: the bundle already ships DESIGN.md at root, and a second copy is a second thing that can drift. The three wirings compose rather than compete — the paste-in, the scoped .mdc layer, and the skill, which carries the multi-target workflow a rules file structurally cannot.
• Check 21 — the document's own version line — check 14 is called one version, five places. The spec calls a sixth place the source of truth, and no check covered it. Now one does, comparing the version and its date against the frontmatter.
• The skill becomes installable — amaca-plugin.zip — Agent Plugins 1.0 was published on 6 August by Amazon, Cursor, Microsoft, OpenAI, Vercel and Google: one vendor-neutral way to package agent skills and MCP servers, read by Cursor, OpenAI Codex, GitHub Copilot, VS Code and Kiro. Anthropic is not at that table and Claude Code keeps its own format — but the two manifests live at different paths and never collide, so this is one package with two manifests and a single skill inside, not two packages. Verified, not assumed: claude plugin validate --strict passes clean on the emitted artifact, and it does not see the root plugin.json. The spec ships inside the skill here, in one copy — unlike amaca-ide.zip, whose root is your repo; a plugin root is an install directory nobody browses. CLAUDE.md is deliberately absent: Claude Code fails --strict on it, and says why — context belongs in a skill.
• The repo is now a plugin marketplace — /plugin marketplace add angelomacaione/amaca-design, then /plugin install amaca-design@amaca. The entry installs from the published zip over HTTPS with a SHA-256 pin — no npm, no clone. The pin is not decoration: Agent Plugins defines a package format and leaves distribution, provenance and trust explicitly outside it, so verifiable integrity is the publisher's job. Check 22 recomputes the digest against the bytes on disk, because a hash that nobody re-checks is a hash that goes stale.

Fixed

• The contract declared itself two minors behind, for two releases — the version line read 3.2.0 while the frontmatter and the whole site read 3.4.0. Every stamp the harness could see was correct; the only one it could not see was the one the spec calls canonical.
• Declared debt never came due — the gate suppressed a check whenever a debt was declared, and never compared the release it named to the current version. A debt dated v3.5.0 would have stayed silent at v9.0.0. The mechanism described as declared and dated was only declared — the date was decorative, and 71 open findings would never have surfaced on their own. Deadlines now expire: at or past the release it names, a debt blocks like anything else. Deferring stays legitimate; it has to be done on purpose, by moving the date.
• The release checklist stated its own number of checks, and the number was wrong — step 0 read nineteen against a harness of twenty-one, and this release added three more, so any figure written there would have rotted again within the same version. Step 0 no longer states a count: the harness prints it.

Changed

• The IDE download card and its button — the card read .cursor/rules/amaca.mdc and the button was labelled amaca.mdc, a file replaced in v3.1.0 by the core / html / react split. The site had been offering a download named after a file that had not existed for three releases.
• llms.txt indexed three AI-tool entry points out of seven — CLAUDE.md, the paste-in, the amaca-frontend skill and the IDE bundle were all missing. An index that omits four of the surfaces it exists to advertise teaches a retrieving agent that they do not exist.
• Debt re-dated to v3.6.0 — the seven css-only registry rows, the teaching-grammar note, and checks 03, 17 and 18. Deliberate deferral, not drift: with the expiry fixed, the new date is a real deadline.

Trigger

A competitive watch found that Cursor had changed its primary input shape in January and nobody noticed, because every run re-read the page about rules — which by construction cannot mention a format arriving beside it. Checking what we actually emit against what Cursor actually reads deflated the alarm and left one real gap. Pointing the same reflex at this repo — verify the artefact, not the description of it — found the other three. All of them had the shape this system knows best: no symptom, and a gate reporting green.

MINOR. The token rule works because the token list is closed. Components had no equivalent list, so a model couldn't tell "not covered" from "not yet written" — it invented. This release closes the component inventory, gives states the same fixed grammar motion got in v3.3.0, and documents seven components that were either shipped-but-invisible or missing entirely.

Added

• Component registry (§ 3.0 of the spec) — the closed inventory of components, with a four-state vocabulary: canonical (spec written) · css-only (shipped in CSS, spec owed, milestone named) · off-system (stop and ask) · site-only (documentation chrome, not the contract). A component not in the table is off-system. This is what makes the token rule executable one level up — a generator can now detect non-coverage instead of inventing.
• State grammar — one fixed six-column schema for every interactive component (state · background · border · foreground · ring · other) with a closed state vocabulary and two RIGID rows: focus-visible is mandatory for anything focusable, error is mandatory for every form control. The state index aggregates every ratified row.
• Stacking scale — seven named layers, from --z-sticky to --z-max. The values name the system as built — nothing was renumbered. A raw z-index of 10 or more is now greppable as a violation.
• Duration by distance (RIGID) — perceived velocity is distance ÷ duration, so a component whose content varies by an order of magnitude cannot have one honest duration. Three buckets, three existing tokens, no computed values: under 120px rides --d-base, 120–600px --d-slow, over 600px --d-scene.
• Teaching grammar — the closed list of the four surfaces a component is documented on: framing prose, Do / Don't, demo caption, contract card. Written after an audit found five competing grammars and no rule saying which to use — 41 of 90 subsections with no framing prose, Do / Don't in 6 sections of 24, and the demo caption doing two incompatible jobs. RIGID: a rule never lives in a demo caption, and a demo with no choreography gets no replay button.
• Browser chrome — scrollbar, ::selection and caret-color promoted from the CSS into the contract, with a closure clause and one ratified exception. The scrollbar had been specified since v1 and had zero occurrences in the spec.
• Date picker — the most complex component in the system, shipped since v2 and invisible in the contract until now — full anatomy, the closed day-flag set, range with two months, presets, year jump.
• Table, Checkbox, Switch — shipped in CSS, never documented. Now canonical, with state matrices.
• Radio, Alert, Toast, Tooltip — four components that existed nowhere. Radio completes the choice-control family (square with a tick, circle with a dot — shape carries meaning before colour). Alert never tints its fill, and is not dismissible at all — not on a timer and not by the reader: a close button would let someone hide a state that is still true. If the reader must be able to make it go away, it is a toast. That is the line between the two components. The icon labels the title, so a titled alert drops its body to a second row aligned with the icon rather than hanging indented off a short label. Toast auto-dismisses only when it carries no action and no error, and enters and leaves on the side it lives on — 24px from the right, the exit retracing the entry on the same axis, differing in speed and not in path. Tooltip opens on hover and on focus, holds no interactive content, and is never the sole carrier of meaning — and at most one is open at a time: opening one closes every other, since two overlapping bubbles make both unreadable.
• .btn-outline — the fifth button variant, shipped in v2 and never listed in the variant table.

Changed

• Input states — three prose bullets replaced by a state matrix. Error is marked with aria-invalid="true" and the border follows from it.
• Focus rings are now named — pressable halo and field glow, so the state grammar cites them instead of re-typing the rgba literal on every row. The choice controls join the pressable list.
• .info-strip → .alert — the un-specced ancestor becomes a deprecated alias. Still works; removal scheduled for v4.0.0.

Fixed

• --font-mono was never a monospaced stack — tokens.css carried a copy of --font-sans while the spec and the DTCG file both declared a real mono stack, a correction applied to the export in v3.1.0 and never propagated to the CSS. The system ran on two typographic identities: 134 token references rendering Satoshi, 38 hardcoded stacks rendering real mono. The CSS was right — Amaca is a single-typeface system and the mono register is Satoshi plus letter-spacing, uppercase and tabular figures. Spec, DTCG and the 38 stacks all realigned; a real monospaced stack is now off-system.
• One duration across a 34× range of distances — the § 15 accordion panel is 60px, the § 24.1 changelog panel is 2037px, and both rode 600ms from the same rule: 100 px/s against 3395 px/s. They read as different components because they were moving at different speeds. Accordion panels now pick their duration token by measured height (§ 08.3) — 206 px/s and 1299 px/s, from the same closed scale. Only the choice is computed; the value is always a token.
• The loader inside .btn-primary was dark while the label was light — the dark silhouette was ratified when the primary label was still dark; § 6.3 flipped the label to near-white two releases later and the loader was never revisited, so the two halves of the same button carried opposite treatments. The rule behind it is now written: anything composed inside .btn-primary wears the label's colour.
• 704 <code> elements ran on the browser's monospaced default — only two were ever styled, so every other inline fragment fell back to a real monospaced typeface. The § 11.2 rules card showed both, a line apart. code, kbd, samp, pre now ride the mono register in the reset.
• The composer's staged state was two rows tall for one line of text — rows="2" left the text at the top and pushed attach and send to the bottom, so the two side-by-side demos didn't match. Shipped that way since the composer landed.
• var(--brand) does not exist — 13 uses — the digit labels in the time and date input rule cards referenced an undeclared token. The fallback was a plausible grey, so it never read as broken.
• 153 raw px in inline styles — swapped to tokens at exact parity. 115 off-scale literals remain, scheduled with the teaching-grammar debt.
• The input error state had no CSS — the spec has promised a danger border since v2.0.0; only the helper text was ever implemented.
• Checkbox and switch had no focus ring — both shipped without :focus-visible — an accessibility floor violation in the two most-used form controls after the text input.
• Raw hex, eight survivors — including two #fff that contradicted the no-pure-white rule fixed for ::selection in v3.3.0. components.css now contains zero raw hex.
• Motion token pairs, seven survivors — transitions carrying a duration with no easing half. The two transition: all on the choice controls are now explicit property lists, so the Spatial-vs-Effects rule is checkable per line.

Trigger

An audit against v3.3.0 found three classes of failure with one root cause. Spec that existed but was invisible in the contract (the scrollbar, specified in CSS, zero mentions in the spec). Components shipped in CSS and never documented (Date picker, Table, Checkbox, Switch) — the model reinvented them though a canon already existed. Components that existed nowhere, so the model invented from scratch. Writing the registry surfaced the second finding: the audit that closes the inventory is also the audit that finds the drift — eight raw hex, seven half-written token pairs, two missing focus rings, and an error state documented for four versions but never implemented.

MINOR. The motion documentation becomes homogeneous: one fixed grammar for every component that moves, two new RIGID rules, and the anti-drift net extended to catch what it couldn't see. Shaped by a comparative research pass across M3 Expressive, Figma, Carbon, Atlassian, Fluent 2, Polaris and the DTCG standard. No token value changes.

New · Motion grammar (§ 08.3–08.4)

• Spatial vs Effects (RIGID) — every animated property has a type, and the type gates the easing: spatial (transform, position, size, shape) may ride any curve including --ease-spring; effect (color, background, opacity, shadow) never overshoots. Mechanically greppable, per line.
• Trigger-based pairing — user-triggered states ride --d-quick · --ease-standard; system-triggered transitions ride --d-base · --ease-decel. The trigger decides, not taste.
• Per-component motion schema — one fixed four-column table (trigger · property+type · token pair · reduced-motion, closed vocabulary instant/fade-only/none) replaces prose specs. Card, Accordion, Tabs, Lightbox, Chat, Loader and Diagrams migrated; § 16.4 and § 18.5 converted to the canonical columns.
• Motion index — the aggregate of every ratified per-component spec, in § 08.4 and DESIGN.md § Motion: the system's whole choreography in one table.
• Continuous loops (ratified class) — loops run while mounted, on per-component literal clocks, linear/steps only, each ratified by its own index row (brand mark, fallback ring, label cycle, shimmer, caret). The raw-duration grep exception is now a closed list.
• § 08.3 Easing tokens — the four curves get their own table on the site (they lived only in DESIGN.md and the demo), each with intent annotation on the row.

Changed · Enforcement

The grep audit, the anti-patterns table and AI-agent rule #6 now catch raw ms durations (ratified loops excepted) and --ease-spring on effect properties. Propagated to every download surface: AI-INSTRUCTIONS, CLAUDE.md, AGENTS.md, Copilot/Cursor rules, llms-full.txt; amaca-figma reaches v1.4 (check 8 gains the Spatial/Effects RIGID); the amaca-frontend bundle re-bakes with the pairing section and new checks (H8, R10, F9–F10), and FIGMA.md v1.1 maps the motion scale to Figma's native Timing and Easing variable types.

Fixed

• Vercel Web Analytics — the tracking snippet (PR #9, May 12) was lost in a later index.html rewrite; the site shipped without it and the dashboard read zero. Re-added before </body>.
• Token drift, three survivors — [data-fade] rode a raw 600ms → --d-slow; the law-card bar rode a raw bezier → --ease-standard and a 1100ms clip-path → --d-draw, closing the last off-scale draw-on literal the v2.7.0 audit had missed.
• Changelog renumbered to strict SemVer — v2.4.1 → v2.4.0, v1.2.6 → v1.2.0, v1.1.4 → v1.1.0: the first release of each line is now X.Y.0, consolidation notes and COMPARE links updated. The public sequence has no skipped numbers.
• § Overview metadata stamp — read Version 3.1.0 · Jul 6 while the system shipped 3.2.0: realigned, and the release checklist in DESIGN.md § Versioning now names it explicitly so it can't drift again.

Trigger

The foundations lived in § 08 but per-component motion rules were scattered across component sections with no uniform grammar — the exact pathology a machine-readable system can't afford. A verified research pass over how the leading systems structure motion (spring schemes, composite tokens, intent annotations, kill-switch contracts) shaped the schema; the strongest patterns — Atlassian's intent bundles, M3's spatial/effects taxonomy, Polaris's per-token guidance — landed as Amaca rules.

MINOR. The system reaches the Figma canvas: an in-canvas custom skill for the Figma agent, on the Agent Skills single-file standard. No token, value, or component contract changed.

New · Figma agent skill — /amaca-figma

• Two entry points — generate builds on canvas binding Amaca-named Variables; audit lints a selection on canvas evidence: bindings, token existence, the 85/10/5 budget, contrast pairs, the component registry, type and spacing scale.
• Verify loop — audit runs after every generate; repairs target only the flagged nodes, capped at two passes. A finding that survives a repair is treated as a system gap and routed to the gap protocol, not another loop.
• Fetch-first, fail-stop — the skill reads /llms-full.txt before any action and refuses to generate from memory. It never invents a hex, px, or easing.
• Install — in a Figma file: prompt box → Skills → Add skill → upload amaca-figma.md → invoke /amaca-figma. Ships as downloads/amaca-figma.md + zips/amaca-figma.zip.

New · Motion rule — stat count-up (RIGID)

Numeric stats and KPI values count up from zero to the target on entrance (--d-draw · --ease-decel) and land exactly on the final value; under reduced motion they jump straight to it. Already the site's counter behavior — now normative in § 08 for every deploy target, taught by the amaca-frontend targets (v1.1.9) and audited by /amaca-figma (check 10).

Changed · downloads grid (§ 03.0)

• Hero swap — the Figma card takes the second hero slot; AGENTS.md moves to the top of the AI integrations column. Its bundle is unchanged.
• Builders card — Figma Make hands off to the dedicated Figma card; the row now reads v0 · Lovable · Base44. Same paste-in bundle (amaca-appbuilder.zip), contents unchanged.
• § 03 instructions reconciled — the install rows now mirror the hero cards: the Figma row teaches the in-canvas skill (install like Claude, invoke /amaca-figma) and a Google Stitch row is added; the IDE row reflects the v3.1.0 core + per-target layout; the spec-contents table speaks the design.md grammar; versioning cards refreshed (CURRENT v1.1.9); subsection numbering closed (03.1–03.5, was 03.2–03.6).
• tokens.dtcg.json → DTCG stable 2025.10 — colors as colorSpace/components objects (hex kept as fallback), dimensions and durations as value+unit objects, easings as cubicBezier arrays, shadows structured, font stacks as arrays. Repairs in passing: two gradient tokens re-typed from cubicBezier to other, font-mono corrected to the ui-monospace stack, em letter-spacing kept as strings (dimension is px|rem only). The draft-format file remains in git history.
• llms-full.txt version stamp — the self-contained context file now declares the spec version and release date it was baked from, so fetch-first consumers (this skill included) can echo what they loaded.

Trigger

Post-Config 2026 the Figma agent accepts custom skills on the same Agent Skills standard this repo already targets — the deliverable is loadable as-is. Occupying the in-canvas surface extends multi-deploy to where designers work. The skill is advisory by nature (the agent is non-deterministic); the deterministic gate remains the amaca-frontend bundle.

MINOR. Two amaca.design-side parity moves — no token, value, or component contract changed. The flagship now ships what the amaca.ai compiler emits.

New · IDE download — core + per-target rules

• Cursor split — the single .cursor/rules/amaca.mdc is replaced by amaca-core.mdc (alwaysApply: true — token discipline, the laws, the a11y floor) plus glob-scoped amaca-html.mdc (CSS/HTML) and amaca-react.mdc (JSX/TSX, Tailwind v4 @theme). The core stays loaded everywhere; the heavy target rules attach only to the files they govern.
• Copilot per-target — .github/copilot-instructions.md (repo-wide) plus .github/instructions/amaca-{html,react}.instructions.md with applyTo globs.
• Canonical targets — html · react · figma. Figma is a Variables deploy, not a glob target, so it carries no .mdc.

New · site /llms.txt

• Curated AI index — /llms.txt points agents at the docs worth reading (DESIGN.md, tokens.css, theme.css, tokens.dtcg.json, AGENTS.md) by absolute URL, plus a self-contained /llms-full.txt with the rules and full token table inlined. Read by Cursor, Copilot, and Claude/Perplexity in retrieval.
• robots.txt + sitemap.xml — permissive crawl policy that names the AI/LLM crawlers (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-Web, PerplexityBot, Google-Extended) as allowed so /llms.txt is never moot, plus a sitemap listing / and /DESIGN.md. Independent layers from llms.txt (access + search vs inference-time index).

Changed · downloads

• App-builder bundle split out — the App-builder card (Figma Make · v0 · Lovable · Base44 · Bolt) now downloads its own amaca-appbuilder.zip instead of sharing amaca-chat.zip, so the two no longer collide as one filename. Both ship the same self-contained AI-INSTRUCTIONS.md paste-in, baked from one source via build-paste-in-bundles.sh — edit once, both stay in sync.

Trigger

Reconciling the hand-authored gold against the compiler's current output surfaced two gaps: the IDE download was a single rule file where the product emits core + per-target, and the site had no hosted llms.txt. Closing those pulled in the adjacent AI-surface hygiene (robots/sitemap) and a download-naming dedupe (App-builder). All close to parity — the flagship eats its own output.

MAJOR. A document-grammar break, not a token change. DESIGN.md is rewritten to the Google Labs design.md open standard — the eight canonical sections in order plus a structured front-matter token block — so any conforming consumer (Stitch, an agent, the amaca-compiler conformance lint) reads it as a valid design.md by construction, not by omission. No token, value, or component contract changed; every screen renders identically to v2.8.0.

Changed

• Eight canonical sections — Overview · Colors · Typography · Layout · Elevation & Depth · Shapes · Components · Do's and Don'ts, in that order. The old numbered sections fold in: Principles / Voice / 85·10·5 / Anti-patterns → Do's and Don'ts; the token sub-sections → Colors / Typography / Layout / Elevation & Depth / Shapes; component specs → Components.
• Structured front-matter — Machine-readable colors: (with an explicit primary: #F051D5 role + the full obsidian/magenta scales), typography:, spacing:, rounded:. The primary role is the load-bearing bit: without it a consumer can regenerate the palette and ignore the brand.
• Extension sections, preserved — Motion, Iconography, Accessibility, Code conventions, Multi-deploy and IDE integration are kept verbatim as marked extension sections after the canonical eight — the richness the standard has no slot for, lint-safe.

Migration

Section numbers changed. In-prose cross-references written as "§ N.M" now point to the same content under its new home (e.g. former § 3.10 Dropdown → Components → Dropdown / Select; § 6.3 → Accessibility → Ratified exceptions; § 2.8 → Motion). A migration note in the spec changelog carries the mapping.

Trigger

amaca.design is the dogfood for amaca-compiler: what the site ships should equal what the compiler emits when it ingests this system. The compiler's output already conforms to the Google design.md grammar — so the hand-authored spec was restructured to the same standard, written at its best. The site is now the maximal-compliant instance, not a bespoke doc the lint can't read.

Also shipped in 3.0.0

• New component · Presentations — slide-deck templates (a fixed 1920×1080 canvas scaled to 16:9, eight layouts), with a live demo deck + layout gallery in Applied. Slide pieces enter on the system's staggered-reveal motion: numeric values count up, listed rows choreograph one at a time, data bars wipe in.
• Downloads · "Pick your tool" — your design system compiled for every tool: a Claude skill + CLAUDE.md, the universal AGENTS.md, Google design.md, IDE rules (Cursor .mdc / Copilot), a self-contained paste-in for ChatGPT/Gemini/builders, and the token formats (Tailwind @theme, raw CSS, DTCG). One turnkey bundle per tool, each with a usage README inside.
• Data Viz · interactive hex world map (§ 19.8) — the public-domain Natural Earth 1:110m land rasterised into a token-styled honeycomb (d3-geo + world-atlas), status nodes placed at true longitude/latitude, click-to-inspect node card, labeled legend.

MINOR. One component refinement: the custom listbox now places itself so it never covers the content it sits above.

Changed · Dropdown / Select

• Viewport-aware placement (variant B) — The custom listbox opens below the trigger and flips above when there isn't room, clamps its max-height to the available space (internal scroll) and clamps horizontally — so the menu never covers adjacent content (e.g. a chat composer the control sits above). position:fixed measured from the trigger's rect when near a viewport edge; the old position:absolute; top:calc(100% + 4px) stays valid only when there's always room below.
• Native <select> (variant A) discouraged directly above content — The browser/OS renders the option popup over the control and can cover what's beneath it; near a viewport edge or above must-see content, reach for variant B.
• Dismissal extended — A fixed-position menu also closes on scroll and resize (its anchored coordinates would otherwise drift from the trigger).

Trigger

A native <select> sitting just above a chat composer covered the input with its option popup. The fix is a placement contract, ratified into § Components → Dropdown / Select, that any control near a viewport edge or above must-see content follows.

PATCH. A ratified no-change: the primary button label was evaluated at three weights and stays Medium 500 — documented so the decision has a date and a rationale, not just a habit.

Ratified

• § 3.1 · Primary label weight — Compared Regular 400, Medium 500 and Bold 700 in context (15px and 13px scales). Under APCA stroke weight is a contrast input and 700 scores strongest — but the bold label shifts the button's voice, and the legibility budget is already carried by the § 6.3 pairing. Medium 500 holds: don't bold the primary label for emphasis, don't drop below 500. Noted in the § 6.3 APCA evidence so the question doesn't reopen.
• System constraint, recorded — Satoshi ships no SemiBold cut: font-weight: 600 silently resolves to Bold 700. The real choice on this system is 500 vs 700.

Skill

Bundle re-baked as v1.1.5 on this spec; HTML.md's a11y note carries the weight rule.

Trigger

Follow-up to the v2.7.1 APCA work: would a semibold label improve accessibility? WCAG 2 is weight-blind, APCA rewards weight, the system has no 600 cut — a side-by-side evaluation closed the question in Medium's favor.

PATCH. Documentation and one token-value refinement. The floor's only ratified exception (§ 6.3, primary button label) gets quantified with the WCAG 3 candidate method — and the perceptual model agrees with the choice.

Fixed

• § 6.3 · APCA evidence — Under APCA the ranking inverts: --obsidian-050 on --magenta-500 scores Lc 55.8 vs 47.4 for the dark label. WCAG 2.x under-estimates light text on saturated mid-tone fills (the "orange button" failure mode). Added with it: the ceiling note (4.5:1 is unreachable on #F051D5 — pure white tops at 3.07:1) and a compliance mode for AA-contractual contexts (dark-label variant, on request, never default).
• Ratio honesty — The declared ≈3.0:1 was the measured 2.83. Corrected to ≈2.8:1 in every living section (§ 3.1, § 6.1, § 6.3 spec · § 03.4, § 21.1 site). Historical changelog untouched.
• § 21.1 · EXC badge — Dropped the warning tint: the asterisk already marks the exception, and semantic colors are feedback-only (§ 04.5) — a documentation badge reading as an alarm was off-doctrine.
• ::selection literal — tokens.css carried color:#fff, contradicting the no-#FFF rule and § 6.3's "near-white" description of the precedent. Now var(--obsidian-050).
• § 7.3 · Runtime-token anti-drift, codified — Live in two domains (Mermaid theming § 18, the window.__motion helper) but missing as a general rule. Now canonical in code conventions: tokens read off :root at every JS boundary; a hand-copied value is a regression.

Skill

Bundle re-baked as v1.1.4 on this spec; HTML.md's a11y note carries the APCA evidence and the measured ratio. Release rule, now standing: every relevant DS change ships into the skill in the same release.

Trigger

An accessibility question — is there an accessible non-pure white on magenta-500? — led to measuring the exception with both models. No light color can pass WCAG 2 on this fill; APCA inverts the ranking in the light label's favor. The floor's only exception is now its most evidence-based section.

MINOR. A motion audit (2026-06-11) found the system's animations running on six engines with two structural leaks: Motion One blocks duplicated easing values as literals and escaped the reduced-motion kill-switch, and chart draw-on choreography lived off-scale. This release closes both — one new token, zero new engines.

Added · tokens

• --d-draw · 1200ms — Sixth duration. Data draw-on: chart tracing, count-up, progressive data reveals. The scale topped out at --d-scene (900ms, hero reveals), but a line tracing itself or a number counting up is a different semantic category — data revealing, not UI entering — and lives naturally at 1.2s. Projected to Tailwind as duration-draw via theme.css.

Fixed · motion integrity

• Motion tokens, one source — The Motion One module now reads --d-* and --ease-* off :root at runtime and hands them to consumers (same pattern § 18 uses for color). The hand-copied easing arrays in cards (§ 12) and data viz (§ 19) are gone — if a token moves, the JS follows. The v2.0.0 lesson, finally encoded.
• Reduced-motion gate for Motion One — The § 21.3 CSS kill-switch can't reach WAAPI/JS animation. Every animate() call is now gated: under prefers-reduced-motion: reduce it jumps straight to the final state and counters land on their target. Cards and data viz — the most animated surfaces in the system — were the only blocks without a JS check.
• Durations snapped to scale — Data viz literals (0.5 / 0.7 / 0.75 / 0.9 / 1.2 / 1.4s) now resolve to tokens: draw-on and count-up ride --d-draw, baseline sweeps ride --d-scene, bar and ramp reveals ride --d-slow. Choreography delays and staggers stay literal by design — they are composition, not vocabulary.
• § 08 demo fallback — playMotion fell back to cubic-bezier(0.2, 0.8, 0.2, 1) — a curve that exists nowhere in the system — and 240ms, the pre-v2.0.0 base. Now reads --ease-standard and --d-quick off :root.

Trigger

An external motion audit read every animation path in the codebase and found the virtuous pattern — tokens read off :root at runtime — already canonized in § 18, while the Motion One blocks next to it still carried hand-copied values. Extending the system's own best pattern to its most animated surfaces is the whole release.

PATCH. Documentation-only. The accessibility exception ratified in v2.6.0 (§ 3.1 primary button label) is now reflected everywhere the old rule survived. No token changes, no component API breaks — every screen renders identically to v2.6.0.

Fixed

• § 03.4 · A11Y floor — Rewritten. The old note required obsidian-950 on every magenta fill and called light text a failure; it now states the dark-text default and documents the single ratified exception, scoped to .btn-primary.
• § 21.1 · Contrast pairs — The obsidian-900 on magenta-500 row described the pre-v2.6.0 button. Replaced with two rows: obsidian-050 on magenta-500 (≈3.0:1, ratified exception, primary button label) and obsidian-950 on magenta-500 (6.5:1, AA, default for every other magenta fill). Section lede updated — "nothing falls below AA" is no longer literally true, so it no longer says it.
• § 02 · Principles heading — "Five rules. No exceptions." violated § 20.4 (no exceptions as rhetorical emphasis) and, after v2.6.0, was literally false. Retitled: "Five rules. Exceptions earn their keep."
• § 02 · Signature curve copy — Still claimed every surface rides cubic-bezier(0.16, 1, 0.3, 1); since v2.0.0 that curve lives at --ease-decel and --ease-standard is the Framer ease. The copy now says what the tokens say.
• § 03 · Skill references — The docs described the skill as v1.1.0, 6 steps, 13 checks; the shipped bundle is two releases ahead — 7 steps and 14 checks since v1.1. All § 03 references reconciled, and the bundle re-baked as v1.1.2 on the v2.6.1 spec so the download matches the page that describes it.
• styles/theme.css — v2.5.0 declared it shipped; it never reached the repo. It now exists: a Tailwind v4 @theme projection of tokens.css — var() aliases, zero duplicated literals, same-name tokens (--font-*, --ease-*) declared @theme inline to avoid circular aliases. Verified against a real Tailwind v4 build: 21/21 utilities generate. One spec correction landed with it: the duration namespace in § 13.1 is --transition-duration-*, not --duration-* — the generated utility (duration-quick) is unchanged.

Trigger

An external audit (2026-06-11) read the live document end to end and found three sections still describing the system as it was before v2.0.0 and v2.6.0. A spec that sells enforcement can't disagree with itself — reconciling the copy to the ratified decisions is the whole release.

MINOR. A new component: auto-layout flowcharts and system-architecture diagrams, rendered from a textual source and themed entirely from tokens. Additive — tokens.css is untouched and no component API breaks.

Added · components

• § 18 · Diagrams — Flowcharts / node-edge graphs and system architecture (box-and-line with grouping), via an auto-layout library (Mermaid, theme base) laid out with the ELK engine for orthogonal, FigJam-style right-angle edges (dagre fallback). The theming config holds zero hardcoded hex: tokens are read off :root with getComputedStyle at runtime and passed into themeVariables, and the focus / state classDef strings are built from the same tokens at render time — the source of truth stays tokens.css. 85/10/5 holds: everything neutral obsidian, exactly one --magenta-500 focus node per diagram; semantic states (--success / --warning / --danger) only when a node encodes a real state, always with a distinct shape + label + a .diagram-legend — never color alone. Anatomy: <figure class="diagram"> → .diagram-canvas[role="img"] holding the SVG → .diagram-caption (FIG-NN · title), coherent with .card.

Motion

• On-scroll entrance — Reuses the established reveal patterns. An IntersectionObserver (threshold 0.15, rootMargin '0px 0px -8% 0px', unobserve after fire) cascades nodes in (~70ms stagger), then edges and clusters. Opacity only — no CSS transform on the generated SVG <g> groups; they compose with the cascade and break the auto-layout positioning. Hooked after the async render resolves. prefers-reduced-motion: reduce renders straight to rest.

Refined

• § 3.1 · Button (primary) — Primary label moves dark → near-white: --obsidian-050 on --magenta-500. A ratified accessibility exception (§ 6.3): the pair is ≈ 3.0 : 1, below the 4.5 : 1 AA bar, kept on perceptual grounds — on the high-chroma magenta, near-white separates more cleanly than the higher-contrast dark label. Scoped to .btn-primary; rest and hover are bounded to --magenta-500 (no lighten), fill and dual-ring focus unchanged. The CTA stays --magenta-500, so the magenta doctrine and chat reservation are untouched.
• Section numbering — Diagrams lands in the Components group as § 18. The Applied and Meta groups shift by one — Data Viz 18→19, Voice 19→20, Accessibility 20→21, Case Study 21→22, Changelog 22→23. Sidebar nav, in-page anchors, and cross-references all updated; no external links break.

Trigger

The multi-deploy docs (v2.5.0) needed a system map and there was no on-system way to draw one. The open question — how to theme an auto-layout library without pasting hex into its config — is closed by reading tokens off :root at runtime. That is the rationale for § 18.

MINOR. React and Figma move from roadmap to shipped. One canonical token now projects to three surfaces — CSS, Tailwind v4, Figma Variables — defined in a new § 13 and emitted by styles/theme.css. Additive: tokens.css and every component spec are untouched; existing HTML output is byte-for-byte identical.

Added

• § 13 · Multi-deploy compatibility — One token, three surfaces. var(--magenta-500) ↔ bg-magenta-500 (React / Tailwind v4) ↔ the Figma Variable color/magenta/500, all resolving to #F051D5. The direction is one-way: tokens are the source, every target derives.
• styles/theme.css — A Tailwind v4 @theme projection of tokens.css. var() aliases, no duplicated literals. Wire it with @import "amaca-design/styles/theme.css" and the full token scale becomes utilities.
• DESIGN.md YAML frontmatter — Machine-parseable header: version, updated, last_synced, deploy_targets. The markdown body is unchanged below it.
• amaca-frontend skill v1.1.0 — Multi-target. Reads HTML.md / REACT.md / FIGMA.md for the surface you request and ingests theme.css for React output. HTML, React via Tailwind v4 @theme, and Figma Variables all ship.

Refined

• § 03.5 · Multi-deploy export — Reframed from roadmap to shipped. The section now documents the three-surface model and the theme.css import. The Google design.md open-spec dependency is dropped — the React/Tailwind path is Tailwind v4 @theme native, not generated by an external tool. The DTCG export is restated as Amaca's own roadmap, fully decoupled.
• Version reconciliation — Spec, skill, header badge, and overview meta all reconciled to v2.5.0 / skill v1.1.0. § 03.1 and § 03.6 reflect the multi-target skill and the spec ↔ skill version split.

Trigger

The amaca-frontend skill reached v1.1 and its reference docs cited a § 13 and a Tailwind v4 @theme projection that did not yet exist — the skill shipped ahead of its contract. § 13 and theme.css close that gap: the contract the skill already references is now real and canonical.

PATCH on top of a documentation refresh. The § 03 Meta surface is rewritten end-to-end: two delivery formats (skill bundle + raw spec), per-runtime install guide, model capability tier, and the Tailwind / DTCG export roadmap. No token changes, no component API breaks — every screen in the system renders identically to v2.3.0.

Added · documentation

• § 03.1 · Choose your fit — Two formats, two postures. The amaca-frontend.skill bundle (and universal .zip mirror) for Cowork and Anthropic-stack runtimes — a 6-step workflow, 13 verification checks, gap-surfacing protocol. The raw DESIGN.md for any chat model that takes a system prompt. Both wrap the same spec; the skill enforces it at generation time.
• § 03.2 · How to install — Per-runtime instructions for Cowork / Claude Code, Cursor / Continue / Windsurf / Aider, Gemini Gems, ChatGPT Custom GPT, and one-off chat attachment. The five rows replace the previous three generic workflows.
• § 03.4 · Model capability tier — New section. Frontier vs lightweight expectations, with measured scores (8.5/10 overall, 9.5/10 on gap handling across N=4 scenarios on the Anthropic stack), the 30-second post-generation scan checklist, and the runtime architecture caveat for consumer chat tools that abstract file grounding.
• § 03.5 · Tailwind export — Roadmap. When YAML frontmatter lands in DESIGN.md v2.5.0+, three tooling integrations unlock via the Google design.md open spec: lint (token references, WCAG AA contrast, orphans, section order), diff (token-level regression detection), and CSS export to Tailwind v4 @theme or W3C DTCG tokens.json. v1.1 of the skill adds React-via-Tailwind generation on top.
• § 03.6 · Versioning & license — Two SemVer streams, documented. The spec follows the system release; the skill versions independently and ships with whichever DESIGN.md is current. License stays MIT.

Refined

• Page-level framing — § 03 retitled from "packaged for machines" to "two ways to drop it into your stack." The lede now names the spec/skill split up front instead of pitching a single Markdown file.
• § 03.3 · Components row — The "what's inside" table now states 13 components explicitly (buttons, forms, cards, badges, navigation, accordion, chat, loader, checkbox, …) rather than the earlier abbreviated list. Cross-reference to Changelog bumped to § 23 to match current numbering.

Fixed

• Stray markup in versioning copy — The old § 03.4 versioning card had a duplicated </p> closing tag mid-sentence (a paste artifact from an earlier draft). Replaced by the rewritten § 03.6 block.
• Spacing token in § 03.1 picker cards — Initial pass used var(--s-7), which is not part of the 4-px scale (the system skips 7) and resolved to 0px. Cards now use var(--s-8) for full padding.

Trigger

Operating the system across multiple AI runtimes — Cowork, Cursor, ChatGPT, Gemini — surfaced a single point of friction: the docs assumed one delivery mode (paste the spec) when in practice two exist, with very different enforcement guarantees. v2.4.0 closes that gap and pre-loads the v2.5.0+ Tailwind roadmap so the next minor release lands against a documented surface, not a blank one.

MINOR release. Two new components ship — a chat & messaging set built for chatbot interfaces, and a brand-logo loader at four scales with five composition variants. The 85/10/5 law card gets an entrance choreography. The Applied and Meta groups renumber by one to keep Components contiguous (16 Chat, 17 Loader); no token, no API breaks.

Added · components

• § 16 · Chat & Messaging — Bot and own bubbles at uniform --r-lg (no tail), avatar on the first bubble of a bot streak, two-stage entry choreography (container scale(0.92→1) on --ease-spring at --d-base, inner content fades up 80ms behind on --ease-standard), typing indicator with a 3-dot wave loop on --d-slow, scripted live demo with replay, full composer specimen (textarea + send + attach). Own bubbles fill with --magenta-700 so --magenta-500 stays reserved for CTAs and focus.
• § 17 · Loader — Brand mark (Lottie/GIF) at four scales — --loader-xs 16 / --loader-sm 24 / --loader-md 48 / --loader-lg 96. Five variants: standalone, with-label (cycling phrases on a 2.4s interval), inside-button (replaces label when .is-loading), skeleton handoff, and success state with a check that scales in on --ease-spring. Four real-world compositions: form submit, async input validation, full-page boot in a device frame, and a cross-component placement inside the chat composer. Under prefers-reduced-motion: reduce the brand mark steps aside and a single magenta CSS ring spinner takes its place.

Added · tokens

• --loader-xs / sm / md / lg — Component-specific size scale at 16 / 24 / 48 / 96px. Lives in tokens.css alongside layout tokens.

Refined

• § 04.7 · 85/10/5 law card — Entrance choreography added. On scroll into view, the proportion bar wipes left-to-right via clip-path: inset(0 100% 0 0) → inset(0 0 0 0) on --ease-decel, then the three legend rows and the rule block fade-and-rise in sequence (stagger 180ms). IntersectionObserver fires once at threshold 0.25; reduced-motion users see the resolved state instantly.
• Chat own-bubble color — Discarded the "hot last" rule (latest own message tinted bright magenta). Unified all own bubbles on --magenta-700 (deep brand) with --obsidian-050 text — 6.26:1 contrast, near-AAA at body size. The brighter --magenta-500 stays reserved for CTAs and focus rings, so the 85/10/5 budget holds in long conversations.
• Loader inside .btn-primary — Cyan-on-magenta is off-system. Resolved via filter: brightness(0) on .btn-primary .loader-anim, collapsing the cubes to a near-black silhouette without introducing a second source file. Applies at rest and while loading.
• Section numbering — Applied (Data Viz, Voice, Accessibility, Case Study) and Meta (Changelog) groups shift by one — 16→18 / 17→19 / 18→20 / 19→21 / 20→22 — to make room for the two new Components entries. Sidebar nav, in-page anchors, and cross-references all updated; no external links break.

Accessibility

• Chat conversation — The scroll region carries role="log" aria-live="polite" aria-relevant="additions"; each bubble includes a visually-hidden sender prefix ("Amaca said:" / "You said:") so the read order survives when the avatar is suppressed on streak follow-ups; the typing bubble carries aria-label="Amaca is typing"; the composer textareas get a persistent aria-label.
• Focus visibility — Dual-ring focus state (--obsidian-100 outline + magenta halo) added to .chat-composer-attach, .chat-composer-send, and .chat-demo-replay. Touch hit areas on composer buttons bump from 36 to 44px below 720px wide.
• Loader semantics — Every loader carries role="status" with a contextual aria-label. The cycling label variant updates the host's aria-label in lockstep with the visible phrase, so screen readers hear the real wait rather than a generic "Loading".

MINOR release. Three new components ship: a calendar-popover date input, a two-month date-range picker with analytics presets, and an iOS-style scroll-wheel time picker. The release also closes two spec gaps surfaced by a real implementation (pipeline-dashboard, 2026-05-12): Tabs were under-specified and the dropdown / select pattern was missing entirely.

Added · components

• § 11.2 Time picker — iOS-style scroll wheel. 24h, configurable minute step (default 5), 7 visible items, infinite loop via triple-buffer + auto-rewind, native scroll-snap-type: y mandatory. Magenta band overlay + top/bottom fade gradient. Click on item snaps with smooth scroll; ↑/↓ on a focused wheel step ±one. ↓ on the input opens the popover.
• § 11.3 Date input — DD/MM/YYYY single date. Digit-by-digit masked (D1≤3, D2 depends on D1, M1≤1, M2 depends on M1, slashes auto-insert). Trailing calendar icon opens a popover with year-jump view (decade grid 4×3), Today shortcut, optional data-min/data-max bounds. Real-date validation (31/02 rejected) fires on blur.
• § 11.4 Date range — Two coupled inputs (data-range-start / data-range-end) sharing one popover anchored to start. Two months side-by-side; collapses to stacked vertical under 600px. Click 1 sets start, hover preview, click 2 commits end (swaps if before start). Four analytics presets in footer: Today, Last 7 days, Last 30 days, Last month. Helper auto-renders N days (inclusive count).

Refined · spec gaps closed

• § 3.7 Tabs — Expanded from a single line to a full spec: canonical HTML, required classes, the indicator-positioning JS pattern (getBoundingClientRect on button + parent, transform: translateX + width interpolation, resize listener, double requestAnimationFrame for initial position), prefers-reduced-motion handling, panel fade-in with opacity + 6px translateY, and the "never crossfade, never slide both" rule.
• § 3.10 Dropdown / Select — New section. Two variants: native enhanced (<select class="select"> with appearance:none + inline SVG chevron, canonical stroke %238A94A3, 36px right-pad, hover/focus borders) and custom listbox (.select-wrap > .select-trigger + .select-menu > .select-option) with full keyboard nav, focus-trap, click-outside dismissal, and guidance on when to prefer each.

Fixed

• Date picker hover flicker — The :hover rule on .dp-day now excludes every range state (is-in-range, is-range-preview, is-range-start, is-range-end); previously obsidian-800 was overpainting the magenta range fills frame-by-frame.
• Range second-click reliability — The hover preview no longer re-renders DOM (was destroying the cell under the cursor before click could register). Cells are cached on grid._cells and only their state classes get repainted via paintRange(). Commit moved from click to mousedown with preventDefault.
• Stepper label drift on replay — The reset used a flag shared with dots (_baseT, never set on labels) and re-parsed cy from the already-offset attribute, accumulating +10px per replay. Replaced with a dedicated _labelInit flag and a clean translate(cx, cy) reset.
• Replay button capture phase — Listener moved to capture phase so the chart reset survives any downstream stopPropagation.

Compatibility

Trigger

A real implementation — pipeline-dashboard, 2026-05-12 — surfaced two under-specified areas. Closing those gaps is the rationale for the spec-side updates in § 3.7 and § 3.10.

MINOR release. Adds the first new component since v2.0.0 — a fully-masked time input — alongside deterministic landing-page routing and a stepper transform refactor that fixes a long-standing replay bug. design.md bumped to v2.1.0; drop the new spec into your LLM rules.

Added

• § 11.2 · Time input — HH:MM, 24h. Digit-by-digit masked: H1 max 2, H2 max 3 if H1=2 else 0–9, M1 max 5, M2 0–9. The colon inserts automatically after the second digit. No native type="time" — the browser picker doesn't respect the system. maxlength="5" + inputmode="numeric" are required. Optional by default; can be marked required per context. Focus & error states inherit from § 11.1.

Refined

• Anchor-link routing — landing on amaca.design (no hash) now always resolves to #overview. The previous localStorage fallback that remembered the last-visited section across visits has been removed — fresh visits are deterministic. URL is rewritten via history.replaceState to avoid extra history entries.
• Stepper SVG transforms — refactored to use the SVG transform attribute as the single source of truth (instead of CSS transform-box: fill-box, which v2.0.1 had documented). A generic [data-fade]{transform: translateY(12px)} rule was silently composing with the group transforms via cascade and breaking dot positioning. Replay now drives the SVG attribute directly.
• .law-rule mobile padding — uniform 20px padding on small viewports with a 24px left-pad to compensate for the magenta border. Internal gap reduced from 32px to 12px for compact stacking.

Documented

• § 3.9 — Time input full spec (rules, contract, reference implementation).
• § 7.3 — SVG group transforms guidance rewritten: prefer SVG attribute over CSS. Stepper choreography updated. Anchor-link routing pattern added.

Compatibility

Note on history

v2.1.0 follows v2.0.0 directly. The internal v2.0.1 patch (stepper hardening, outcome card stat refactor, staggered text reveals) was never publicly tagged — its contents are folded into this release alongside the new additions. From v2.1.0 onward the system continues to follow strict SemVer.

First major release. Motion vocabulary recalibrated end to end — easing curves redistributed semantically, durations restretched across the full scale. Everything else stays. One reason to bump the major: one set of changes worth knowing about.

Breaking changes

This release shifts the values of the motion system. Token names are unchanged. If you reference Amaca tokens in another project, audit motion before upgrading.

Easing values reassigned

The four easing tokens kept their names. The curves under them moved to better match what the names mean.

The curve cubic-bezier(0.16, 1, 0.3, 1) — the system signature — now lives where it semantically belongs: --ease-decel. Use it for entrances and reveals, where the slow tail in the curve has always been doing decel work. --ease-standard is now the Framer ease, sized for everyday UI state changes (hover, focus, button press).

Migration: if a component was relying on --ease-standard to behave like the old signature curve, switch it to --ease-decel. If it was using --ease-standard for generic UI feedback, leave it — the new curve does the job.

Duration values rebalanced

The five duration tokens have been restretched. Names unchanged — only values shift. The new scale stretches the slower end (more breathing room on entrances and orchestrated reveals) and grounds the faster end on round numbers.

Migration: no code changes required if you reference durations via var(--d-*). If any duration is hardcoded in milliseconds, search for the old values and confirm intent.

Refined

• Motion — Additional animations integrated across components. The new easing/duration pairings applied throughout.
• § 7 · Grid & Layout — Grid system extended to tablet and mobile breakpoints. Column counts, gutters, and content widths now documented for every viewport.
• § 14 · Voice & Tone — Section rewritten for sharper register. Do/Don't examples expanded. Vocabulary table tightened.
• design.md — Spec file regenerated for v2.0.0. Drop the new version into LLM system prompts to keep AI-generated work in sync with the live system.

Fixed

• Mobile responsiveness — Multiple layout fixes across breakpoints. Long titles, dense tables, and stat cards now behave correctly on narrow viewports.

Compatibility

Note on history

v2.0.0 follows v1.2.0 directly. Internal iterations between (drafts at v1.2.1 and beyond) have been consolidated into this release. From v2.0.0, the system follows strict SemVer with no skipped numbers in public releases.

First substantive expansion since v1.0. The system gains three new components, a full accessibility posture, a public changelog, deep-linkable sections, and a downloadable spec for AI-assisted design.

Added · new components

• § 15 · Accordion — Collapsible content blocks for FAQs, dense documentation, and progressive disclosure. Single-open and multi-open variants. Keyboard navigation built in.
• § 19.5 · Timeline (Gantt) — Horizontal time-based visualization for project phases, roadmaps, and case study chronologies. Date-aware, with milestone markers.
• § 19.6 · Stepper — Linear progress indicator for multi-step flows (forms, onboarding, case study walkthroughs). Horizontal and vertical variants.

Added · new sections

• § 21 · Accessibility — Color pairs with documented contrast ratios, prefers-reduced-motion handling, focus & keyboard order, and hard rules that gate every component decision.
• § 23 · Changelog — Version history, in public. What changed, when, and why.
• § 03 · Documentation — Single Markdown file (design.md) containing every token, component spec, principle, and rule. Built to feed into LLMs as context for AI-assisted design work. Updated alongside the system — every release ships a fresh spec.

Added · navigation

• Anchor links — Every section header now carries a hash. Deep-link any paragraph: amaca.design/#13-accordion, amaca.design/#16-accessibility. The system became citable.

Refined

• § 04 · Colors — Visual presentation refined. Token names, hex values, and intended use unchanged — no breaking changes to consumers.
• § 10 · Buttons — Vertical padding tuned for better optical balance across sizes.
• Copy — Several section intros and microcopy tightened for rhythm.

Added · meta

• Favicon — Amaca mark serves across browser tabs and bookmarks.
• Open Graph image — Link previews on social and chat render the system's identity instead of a generic screenshot.

Unchanged

No token renames. No component API shifts. No breaking changes.

Note on history

This release consolidates internal iterations after v1.1.0 that were not shipped publicly. From v1.2.0 onward, the system follows strict SemVer.

Maintenance release. Small fixes, one meaningful polish pass on donut charts.

Fixed

• § 04 · Colors — Primary token #F051D5 was mislabeled "Cube Cyan" in the palette reference. Corrected to "Magenta" — its actual value for the last nine months.
• § Overview — Page metadata stamp updated (version + date drift).
• Responsiveness — Layout fixes across mobile breakpoints.
• Interactions — Added states for tabs, images, and thumbs.

Refined · § 19.3 Donut charts

Slice geometry rebuilt from stroked arcs to true ring-segment paths.

• All four corners of each slice now render with a real 2px radius (matches rx=2 on bars in § 19.2).
• Inter-slice gap halved from ~6px to ~3px of circumference for tighter visual rhythm.
• Draw-on animation preserved via angular sweep.
• Before — half-circle round caps (13px radius — too soft) or butt caps (sharp — inconsistent with bars).
• After — 2px on all 4 edges. Matches the rest of the data viz vocabulary.

Unchanged

Everything else. No breaking changes, no token renames, no component API shifts.

Infrastructure

• Repository — Cleanup: removed duplicate nested folders and orphaned font/logo files from root.
• Documentation — Added README and LICENSE to public repo.
• Branch protection — Ruleset activated on main (PR-only merges).

Initial public release. Prima pubblicazione pubblica del design system Amaca, live su amaca.design.

Added · Foundations

• Color — Magenta brand range, obsidian neutrals, electric cyan secondary, petrol tertiary, semantic signals.
• Typography — Satoshi as primary typeface across all weights (Light to Black).
• Spacing, radius & shadow — Core layout tokens.
• Motion — 5 durations × 4 easings, all synchronized on cubic-bezier(0.16, 1, 0.3, 1).
• Grid & layout — Foundational structure across breakpoints.

Added · Components

• Buttons — Primary set with full state coverage.
• Inputs & forms — Field, label, and validation patterns.
• Cards — Container variants for content surfaces.
• Badges — Compact status and category markers.
• Navigation — Top-level wayfinding patterns.

Added · Applied

• Data visualization — Charting vocabulary aligned to brand tokens.
• Voice & tone — Editorial direction across surfaces.
• Case study template — Reusable narrative structure for project work.

Principles

Five principles — clarity before cleverness · evidence over opinion · precision is a feeling · quiet then loud · motion is a material.

Infrastructure

• Hosting — Static site on Vercel.
• DNS — Cloudflare.
• Repository — Public on GitHub, MIT License.
• Versioning — SemVer adopted.