HAL — the Human Application Layer
Improve. Repeat. Win.
You name an aim and a customer. You release Workflows onto a line. Work arrives at nodes. Then you study what happened and redesign the system. That is the product — not another inbox.
Improve
Study what happened
Redesign
Change the line
From the customer, back to suppliers and Workflows
Suppliers
A · B · C
not named yet
Receipt
Incoming test
not named yet
Workflow
Qualify and book
released on the line
Distribution
How it is delivered
not named yet
Customer
Who receives it
one named customer
Tests of Workflows and costs sit under the line. Work happens at nodes. The loop redesigns the system.
01 · System
Name the aim. Draw the line.
How Annex Orbis does it · One system per organization
Aim and customer are first-class. Named suppliers sit at the left of the line. One to seven released Workflows create value for that customer. Everything else stays in the catalog until you pin it.
What that feels like
Without an aim there is no system — only departments pulling in their own direction. The System page is that picture. It is not an org chart and not an app switcher.
02 · Workflow
Release a process, not a canvas.
How Annex Orbis does it · Qualify and book · invented example
A Workflow is nodes: system activity, hired agent, human, or wait. On a fictional Leads Q1 line the Qualify and book Workflow might select who is eligible, call and qualify with copy that lives on the lane, wait for a book, and send exceptions to a person.
What that feels like
A hired agent works the Workflow with the tools the Workflow grants. It cannot invent spoken copy and it does not own Voice. Humans release, activate, and approve what requires authority.
03 · Work
A card appears when the run reaches you.
How Annex Orbis does it · Work is not Tasks
Work is assigned by the system when a run arrives at your node. Empty is a real state. It is not a personal to-do list, not a calendar day, and not a worker leaderboard.
What that feels like
You open Work to see what the line has given you now. When nothing is at your node, the page is empty on purpose.
04 · Improve
Study the customer. Redesign the line.
How Annex Orbis does it · Plan · Do · Study · Act
Plan lives in the aim and the released Workflow. Do is Work at the node. Study compares what you predicted with what happened. Act is a proposed change to the Workflow or the System map. A human applies it.
What that feels like
Improve the system, not the blame. Then run the line again. That is Improve. Repeat. Win.
The lineage
We didn’t invent the cycle. We made it the operating system.
The Plan-Do-Study-Act cycle came from Walter Shewhart at Bell Labs in the 1930s. W. Edwards Deming carried it into industry. The reason most organizations skip it is the paperwork: capture what happened, find the pattern, change the Workflow.
Annex Orbis puts that cycle on the system you actually run. The line, the nodes, the work, and the redesign live in one picture. People and hired agents work the same Standard. A human still applies the change.
Depth on Deming lives in Knowledge. The product is the system you operate tomorrow morning.