The method, followed through one product

Eloom guides product development from the initial problem to release. This example shows how three people and their agents use it to design Otter, a fictional drive unit for family cargo bikes.

Otter, a drive unit for family cargo bikes, exploded. An illustration.

An illustration: Otter, its people and its records are invented.

Someone says what it is for

Otter is a drive unit for family cargo bikes, invented for this page. Lena runs the small company that makes it.

She writes down who it is for and what they need. That context is hers to accept: everything below answers to it, and a change that would alter it comes back to her.

Agents draft the rest

Tomás and Aiko join her, with 61 agents between them. Each agent acts for the person whose key it holds. What it does is recorded as that person’s act, and can be undone.

They break Otter down, from the bike to each board and firmware module, and draft needs and requirements at every level, all at once. Each level states only what the level below must achieve.

Every block runs the same loop: need, design, risk, evidence, baseline. All of it is plain text in Otter’s repository, beside the design files, and it compiles on every change, like code.

Rigor goes where people could get hurt

One hazard stands out: the motor keeps pushing after a brake is pulled, with two children in the box. Aiko approves its rating and the safety goal that answers it.

The goal’s rigor flows down the requirements under it, and up the blocks that meet them: the brake inputs, the controller, its board and its brake monitor. The motor, the lights and the display stay light.

Only on that path does a review have to be independent: Aiko’s reviewers read it afresh, briefed and controlled by nobody who designed it. Everywhere else, agents review and merge the work themselves.

A change from deep in the board

At the second build, the gate driver on the controller board is no longer made. One of Tomás’s agents swaps it on a branch, and the change arrives as a diff with its impact beside it.

The board’s files changed, so the results that examined them are stale and the links above it are in question. The display’s results stay current: nothing they examined changed.

Each owner reads their link again and settles it. The brake test runs on the new board, Aiko approves, and the change merges.

Released when every check is current

A release waits until no check is failing or stale, on every block at every level.

Then the baseline freezes the model, the design files and their evidence as one, and Lena releases Otter.

Only as much method as the product calls for

Three settings size it. Depth follows complexity and sets how many levels a product has. Rigor follows consequence, set element by element by the hazards, so only what protects people carries the most. The stage sets by when the evidence must be complete, from the first prototype to production.

A board for your own bench

Three levels and nothing at stake: a brief, a few requirements, its design files with their checks, and a release record.

Otter

Four levels, and high rigor only along the one path that protects the children in the box.

A product of many subsystems

More levels, each subsystem with its owner, and as many protected paths as its hazards call for.

Built from the standards, not on top of them

The method draws on ISO 26262, Automotive SPICE and model-based systems engineering, rebuilt from first principles for a team of people and agents. It maps itself onto each of them for orientation only; Eloom is not certified against them.

The full method

It is written up as a compendium of 15 chapters, about 29,000 words, with worked examples. It is for Eloom's customers and their agents, who read it in Eloom and through its command line.

Accounts are by invitation for now.

  1. 1Manifesto
  2. 2The loop
  3. 3Tailoring
  4. 4Roles and stages
  5. 5The product page
  6. 6Safety
  7. 7Work products
  8. 8How a change flows
  9. 9People and agents
  10. 10Product model
  11. 11Views
  12. 12Complex products
  13. 13Standards
  14. 14Worked examples
  15. 15Glossary