Onengine — the playground

The same drift ran through everything the product shared: rates, onboarding steps, payment methods, coverage areas, the fields an entity carried, every list a dropdown drew from. Statuses were the clearest case.

Work orders carried statuses. So did visits, and so did auto-dispatch. Counted together the values swung between roughly fifteen and fifty depending on who you asked. Status documents sat in Confluence. Statuses sat in Figma, and nobody knew how current they were. The backend held values that did not match the screens, and the same status was drawn differently by different designers on different screens.

Asking cost a round robin. The engineer asked a designer, the designer asked product, product remembered a call but not a document, and everyone went back to the founder. He gave a different list each time. Worn down by the repeated questions, he picked the easiest answer, which left work orders unable to complete their own workflow.

Behind all of it sat a process the team had agreed and quietly stopped following, and several PRDs per module, each written at a different iteration.

So I stopped writing process and wrote behaviour. Each module gets one brief with the same eleven sections, covering entities, flows, screens, statuses and what the PRD did not say.

Every line carries one tag for where it came from:

• stated in the PRD
• clarified later, by a person with a name and a date
• inferred, with the reasoning shown
• covered by a repo convention
• or an open gap, with a number against it

Pattern knowledge generates questions, not content. "No invented fields, statuses, roles, flows, or copy. Ever."

That is why the brief survives a reversal. An overturned decision arrives as a dated clarified line in the gap register, the brief changes, and the screen is rebuilt from the brief instead of from whoever remembers the last meeting.

The playground is that brief running. It is built in layers, from the floor up.

• Tokens. Colour, type, radii and spacing recorded under the names engineers use, so a value gets consumed, not guessed.
• Breakpoints. Where you watch a page react instead of arguing about narrow screens.
• Assets. Card and brand logos and iconography in one place, so nobody redraws one.
• Fields that carry rules. Phone, email, website, currency, percent, number, ZIP and EIN each hold their own pattern. SSN, routing, account and card numbers behave as sensitive fields wherever they appear.
• Components. Clickable, slots and props shown, so a card or a table is composed, not described.
• Product patterns. A details summary, then a work order details summary that other detail pages extend.
• Tables. The chip, the data cells, the wrapper, filter, sort and search.
• Page templates. A new module starts from a page that exists.

Underneath it all, one settings screen holds what everything reads from: every option set, the columns of each module's table, and the appearance of every badge and chip, edited by a product person without code.

Three written workflows, one per role, each with a hard stop.

• Product ingests a PRD and ends at the brief. It never composes a screen and never edits app code.
• Design looks for the brief before anything else and treats it as the spec. An open gap that blocks the screen goes back to the person who can answer it rather than being filled in.
• Delivery audits the repo, then branches, commits, pushes and opens the pull request for people who do not use git, narrating each step in plain language.

A hook refuses any edit made directly on main. The founder runs the same workflows in his own instance, and his output is the team's source of truth.

Every module gets its own brief, and an engineer opens it to find the entity tables. Every field carries its verbatim name, its type and component, whether it is required, its default, its validation rule and error copy, and where a picker's options come from. Statuses are written as a machine, with the allowed values, the transitions the product permits between them, and who triggers each one. The eight work-order statuses now live in one set, and every screen reads them from it.

A page assembled from an existing template is a change, not a build. The founder clicks through his own version the same day.

First feedback used to take four or five days. It takes one or two now, and it is about whether the thing works rather than which pattern it matches.