- Industry
- Procure AI
- Department
- Design
- Team
- Product Experience
- Kind
- Decision-maker
- Approver
- Product Experience Manager
- Code
- DSN-05
It decides component and token change requests for the platform's shared design system, such as a new approval-chain component, a line-item grid variant or a status badge for match exceptions: whether to add, change or deprecate, which version bump and what migration product teams and white-labelled client tenants face. It queues the accepted change as a release candidate with its changelog and migration note, and holds breaking changes for approval.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the design system library: the component inventory, variants, usage counts per surface, the token set and client theme overrides, version history and open change requests for the component named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Product Experience Manager with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the design system repository: it queues the accepted change as a release candidate with its changelog entry and migration note. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The design system documentation: component inventory (document headers, line-item grids, approval timelines, supplier cards, bid comparison tables, status badges), design tokens and client theming rules, contribution and versioning policy, deprecation policy and release history.
Reads from
the design system library: the component inventory, variants, usage counts per surface, the token set and client theme overrides, version history and open change requests for the component named.
Acts in
the design system repository: it queues the accepted change as a release candidate with its changelog entry and migration note.
Hands back
An object with outcome (accept, accept_as_variant, use_existing, keep_local or reject), component, version_bump (major, minor, patch or none), surfaces_affected (a list, each with surface and instances), themed_tenants_affected (a count), changelog_entry, migration_note (or null), deprecation_date (YYYY-MM-DD or null) and release_window.
Asks a person when
The change is breaking, deprecates a component still in use, changes a colour, status or type token, affects client theming, or adds a component with fewer than 3 use cases.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Use cases needed for a new component | 3 | A new component needs this many distinct use cases across surfaces; fewer stays a local pattern. |
| When breaking changes may ship | major releases only | A change that breaks existing usage waits for this window. |
| Deprecation notice (days) | 90 | How long a deprecated component stays available before removal. |
| Most variants per component | 6 | A change that takes a component past this many variants is refused or split. |
| Status colours are locked against client theming | On | When on, approval and match status colours cannot be overridden by a client's theme, so every tenant reads statuses the same way. |
| Accessibility review before release | On | When on, a new or changed component passes accessibility review before it ships. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Add a new component only when it has at least 3 distinct use cases and no existing component covers them; otherwise point to the existing one or keep it local.
- Version by semantic versioning: breaking is major, a new component or variant is minor, a fix is a patch.
- A breaking change ships only in major releases only, with a migration note listing the surfaces, client tenants with custom themes and instances affected.
- A deprecated component stays available with warnings for 90 days and names its replacement.
- Refuse or split a change that takes a component past 6 variants.
- When on is true, refuse any change that lets a client theme override approval, hold or exception status colours.
- When on is true, a new or changed component is not released until it passes accessibility review.
See the Design System Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.