Docs Designing the system 1
The one rule
On this page
Nothing reaches the plant except through a change request. Every change goes through four stages:
| Stage | Who | What happens |
|---|---|---|
| Design | A designer | You draft the change: objects, rules, scripts, services, connections, schedules. Nothing you draft affects the plant yet |
| Review | A reviewer (not you) | Someone else reads the change and passes it, or asks for changes |
| Approval | One representative per department concerned | Each department whose data or process the change touches approves or rejects it |
| Execution | The platform, when its executor says | Once every department has approved, the change waits, approved, for the person named to execute it when you submitted it. When they press Execute, the platform publishes it in one step. No person, and no AI, publishes anything by hand (your organization may have the last approval execute it instead) |
| Verification | Its executor | They check it in the plant, then sign that it works, or report a problem with a picture of the page |


Three things follow from it:
- You never approve your own change, and whoever reviews a change cannot also approve it for a department.
- The departments that approve are worked out for you from what the change touches: its footprint. Change a quality field and Quality approves; change a service that writes lots and the lot's stewards approve.
- Execution is all or nothing. If something the change was drafted against has changed since (someone else's change executed first), execution is refused, and the change is marked failed so you can redo it on top of the new version.


Designers, roles and approvers: three different things
They are easy to mix up, because all three are about "who may". They answer different questions:
| Answers | Set where | Example | |
|---|---|---|---|
| The designer | How does the system work? The objects, fields, policies, screens, layouts | A change request, in the Designer | Dana adds a Picture field to Equipment |
| Roles | Who may do what with the records? A policy ties a role to rights: read, create, write these fields, take these actions | The object's Roles & policies tab; people are given roles in People & departments | Engineers may upload an equipment's picture |
| Stewards and their approvers | Does this change go live? | The object's Stewards tab (departments); each department's approval steps in People & departments | Production signs the change that adds the field |
So, for one change: the designer drafts the field and the policy; the policy's role says who will be able to use it once it is live; the stewards' approvers decide whether it goes live at all.
Two things that catch people out:
- Several teams may design, each in its own space (People & departments → Spaces): its designers change only what is in it; the Designer's own designer role changes everything. Each list on the designer's home has a Space filter (my spaces first), each design shows its space beside its name, and a new one goes into the space the list shows (or yours).
- "designer" and "reviewer" are roles on the Designer itself, not on your objects. A policy can only name roles the object declares. Name another and the draft says Policy "…": its roles must be roles of this object: take that role out of the policy, use one the object has, or add a role to the object and give it to people.
- Holding a role does not make someone an approver, and being an approver gives no right on the records. A quality engineer who approves changes for Quality still needs a role on an object to open its records.