CHIP
Bridge for agentic design systems
Three things on your plate today: cross-platform landscape audit, Q3 roadmap draft, Friday review prep. I'd start with the audit — it's blocking two squads.
Press ⌘K to jump anywhere · ? for shortcuts
Cross-platform · Landscape audit
Three platform squads, three priorities. The roadmap below is a proposal — review and approve to file the tickets and notify the leads.
Action — review the roadmap below, press Approve to file 23 Jira tickets and notify Web/iOS/Android leads.
Parity
BELLA design system · Web + iOS + Android · live
Agent · Standing by
Alerts · 4 potential divergences flagged
CHIP scans repos, Figma, Storybook, Zeroheight every 14m. v1 will scan Slack and Jira too.CHIP recommends Open BELLA-1267 in Jira, assign Android Lead, block landscape merge until parity check passes.
CHIP recommends Swap iOS focus order to match Web tab sequence in Modal landscape variant.
CHIP recommends Regenerate Zeroheight Card page from Storybook v2.14.3 deploy.
CHIP recommends Propagate amber-30 token change to ios-bella/Tokens.swift and android-bella/tokens.kt; flag platform leads for review.
Proposal · Auto
47 Web components updated for landscape last sprint. iOS squad shipped 23. Android squad shipped 0. Each squad chose their own priority without coordination.
Proposal: ranked roadmap of 23 components to align, Jira tickets filed, Storybook + Figma updated, dev leads pinged for approve-gate.
23 Jira tickets filed · 3 dev leads notified · roadmap acknowledged.
Before you approve
Done
To do
Ready
Estimated time
Approve gated until inclusion issues resolved or operator overrides.
Roadmap accepted · 23 tickets filed to Jira · 3 dev leads notified · 2026-04-26 14:03
Today
Inbox · 3 awaiting reply
Email · Web Lead
"Reviewed your landscape audit — one concern about the button focus ring on iOS. Can we sync Friday?"
Slack · #ds-leads
"@elleta — quick Q: are we shipping the Modal landscape variant this sprint or next?"
Linear · BELLA-1233
You were @mentioned by Android Lead in: "Component freeze for Q3 release — are we good?"
Today · 3 events
Coming up · 3 surface in your bridge this week
Watching
Research · Living map
47 sources tracked. The map updates when anyone in the cohort publishes. Click an entry to pull the full piece into the reader pane.
| Tags |
|---|
Friction log · 3 open
Every tool I use is logged here when it breaks my flow. Open entries are dogfooding debt. Resolved entries keep their audit trail. Pink entries are wishlists.
Friction log · Aggregate
50% resolution rate · oldest open: 11 days · last resolved: 7 days ago
All quiet. Even your design system's a bit bored. That's good.
| Action |
|---|
I click a file, it opens in the sidebar, I try to read my code, I lose my place. I don't need it to close. I need it to get out of the way or be narrow enough that reading the main column isn't a fight.
I'm reading a doc, I want to see the next doc. I don't want to be teleported to the OS. Inline preview, same surface, stay with me.
BELLA's [data-theme="dark"] block only flipped semantic tokens. Component foregrounds stayed at #111. SIMULATE DRIFT rendered as an amber box with no label inside.
Resolved · hotfix 2d.5 · 25 component-token overrides · commit cdd396d
A Saturday text exchange that negotiates custody for the next week is a meeting. It has attendees, decisions, outcomes. It should generate a Notion-style meeting page, not live buried in iMessage.
Old flow: click to open proposal, scroll, click diff, click approve, click confirm. Four clicks to say yes. One decision should be one key.
Resolved · stage 2e · single-key approve · A anywhere in scope
Not urgent. Not rational. Not necessary. But one day. When everything else is shipped and the tokens are clean and the rituals are humming — one day the accent will be pink and no one will stop me.
AI-native BELLA · 6 primitives
BELLA already had buttons, cards, chips. Then CHIP needed to render proposals. Diffs. Audit entries. Each primitive below is a moment the system demanded new vocabulary — evidence that an AI-native design system grows from real agent interactions, not aesthetic ambition.
No primitives drafted yet. CHIP will name them as the agent needs them.
Proposal surface. Eyebrow, headline, body, confidence chip, three-button row. One proposal per card.
Born when the agent first proposed a fix.
Drafted · awaiting promotionInline diff with resolved-variant swap. Same geometry collapses drift lines to success message on approve.
Born when "what changed" needed to read at a glance.
Drafted · awaiting promotionSingle-line mono. Timestamp · change · actor. Never wraps. Always visible.
Born when "who approved what" became load-bearing.
Shipped in v0Value with drift-state color flip. Ink at rest, amber on drift, sage on approve.
Born when "how on-spec" became a single number.
Shipped in v0Eyebrow + chip combo. Tells the reader this came from the agent, not the operator. Non-optional on AI content.
Born when human and agent content needed to be told apart.
Drafted · awaiting promotionIn-flight state. Shimmer only. Never more than 3 seconds without a proposal or an "observing" message.
Born when the agent needed to say "thinking" without lying about progress.
Drafted · awaiting promotionAtomic design · 12 components · BELLA
Atoms are single-purpose primitives. Molecules compose atoms into functional patterns. Organisms are AI-native surfaces — born when the agent needed new vocabulary. Parity gaps at any level propagate upward.
Components · Platform parity matrix
0–59 critical · 60–89 attention · 90–100 in spec · — not applicable · Tokens layer underpins every component above. Drift surfaces here within 14m of any platform commit.
Infrastructure · Dependency map
Hierarchical view of BELLA's surfaces. Click any node to inspect its health, last sync, and key metrics. Status colour reflects current parity.
Click any node to inspect its detail. Status colour reflects parity. Healthy = in sync · Stale = sync overdue · Drift = behind master · Critical = blocking ship.
Surfaces · live status
11 surfaces · 7 in sync · 2 drift · 1 stale · 1 not yet wiredCHIP queries Notion via the Cloud Managed Agent + Notion MCP today. Storybook, Figma, Zeroheight, Slack, Jira, Gmail are post-submission engineering — same pattern, same audit-ribbon discipline. Click any row to drill into its history.
Sync cadence · last 7 days
Sync cadence is the heartbeat of parity. Silent platforms drift first.
Coming up · Reviews CHIP will surface
Reviews CHIP will bring to your bridge. Each row is a future moment of attention.
This week · 6 rituals scheduled
April 26 — May 2, 2026
Sun
26
Mon
27
Tue
28
Wed
29
Thu
30
Fri
1
Sat
2
Click any tile to jump to its detail below.
Nothing on the calendar. Add a ritual to begin.
In the lineage of Maggie Appleton's daemon · Projects By IF's trust patterns · Shape of AI's vocabulary · Amelia Wattenberger's embeddings · Luke Wroblewski's structured search · Vitaly Friedman's expert-user dashboards.
Bridge for agentic design systems.
Most design system assistants answer questions. We intervene at the moment decisions are made.
What it is
CHIP is the bridge a design-systems lead opens when their system has drifted across platforms. The agent watches every surface — repos, Figma, Storybook, docs, ticket queues, dev-lead channels — and proposes a roadmap when parity slips. The operator approves, edits, or rejects. Tickets file themselves. Audit logs itself.
Inspiration
Command palette: Linear / Raycast / Arc lineage. Dense data viz: Hitparade.ch, Nadieh Bremer, howmanyplants.com. Tables: Finviz.
In the lineage of
Maggie Appleton's daemon · Projects By IF's trust patterns · Shape of AI's vocabulary · Hardik Pandya's three-layer contract · Nathan Curtis's mechanical specs · Romina Kavčič's MAPE-K loop · Vitaly Friedman's expert-user dashboards.