- Industry
- Oil & Gas
- Department
- Design
- Team
- Product Experience
- Kind
- Decision-maker
- Approver
- Head of Digital Experience
- Code
- DSN-05
It decides change requests for the shared design system used across field apps, control-room displays and fuel-customer apps: whether to add, change or deprecate a component, which version bump it needs and what migration product teams face. Any change to alarm, status or hazard tokens is treated as a management of change and held for approval with the operations owner.
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, its usage across apps and its version history..
- 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 Head of Digital Experience 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: components, tokens, usage counts per app, the alarm and status token set, versioning rules and the deprecation policy.
Reads from
the design system library: the component, its usage across apps and its version history.
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 decision (accept, reject or defer), version_bump, changelog, migration_note and moc_needed.
Asks a person when
The change is breaking or touches alarm, status or hazard tokens.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Use cases for a new component | 3 | Fewer stays local. |
| Breaking changes in | major releases only | When breaking changes ship. |
| Deprecation notice (days) | 90 | Before removal. |
| Alarm tokens need management of change | On | Changes to alarm, status or hazard tokens go through MOC with operations. |
| Accessibility check | On | Before release. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Add a component only with 3 use cases.
- Ship breaking changes in major releases only with 90 days notice.
- Hold any change to alarm, status or hazard tokens for management of change when on is on.
- Check accessibility before release when on is on.
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.