3. The Operating Model

The Portal

Nothing enters the tunnel on a promise.

Many doors, one queue, and an answer within a day.

A tunnel's portal is its entrance: the one place where you go in. The Lens is the intake framework. It turns a request into a signed scope. The Portal is what an organisation agrees to around it: how requests reach the Lens, how fast they get an answer, and who signs what.

	The framework: what the work passes through	The operating model: what the organisation agrees to
Intake	The Lens	The Portal
Delivery	The Accelerator and the Shield	The Crew

The principle

Work reaches a team from everywhere: a meeting, a message, a customer call. The Portal does not close any of those doors. It makes sure every door leads to the same room: a written request, in one queue, with a state, an owner and an answer. A request that never reaches the room was never work, and nobody is accountable for it.

A team that says yes to everyone is not being helpful. If the strategy says there are no spare hands, every quiet yes contradicts it.

How it applies the core

The Portal is not a new principle. It is the core, applied to how an organisation asks for work.

Principle	At the Portal
The Clarity Contract	A request enters only in writing, in five fields. Nobody says yes on the spot. A customer commitment is not signed before an engineering review.
The Same Room	Every channel ends in one queue. Afterwards, nobody can tell which door a request used. This is the Same Room applied to people instead of systems.
The Tunnel	Once work has started, a new request does not go to the team. It goes through the Change Forum and names what it pushes out.
Rigid Mobility	The live-fire lane is the one sanctioned change of path, and it still leaves a record.
Audit Exhaust	No work item, no work. Every decision and every override is on the record.
The Assumption Tax	The third field asks what happens if we do nothing. A request that cannot say is paying the tax up front.

The four rules

If you cannot write it, we cannot build it.Five fields, in the requester's words, not an engineer's reconstruction. Writing a request must be cheap, so a short clinic writes it with you if you get stuck.
Nobody says yes on the spot, and everybody gets an answer within one working day. These are two halves of one rule. Refusing to answer in the moment is only fair because the answer comes fast.
No work item, no work. Capacity, status and reporting come from one system and nowhere else. Creating an item yourself is a request, not a commitment. Only the product owner moves work to Ready.
Talk to us before you sign anything with a customer. Engineering states what a deliverable costs, what it depends on and what is not possible. The commercial decision stays where it is. It is just made with the information.

The only exception: customer-facing incidents beat all four.

The five fields

What do you want to be able to do that you cannot do today?
Who is affected, and how many?
What happens if we do nothing for a quarter?
How will you know it worked?
Is there a deadline, and what drives it?

Inside the one working day: SPEC

Specify. The requester fills in the five fields. The clock starts when they are complete.
Probe. What does it touch, who owns those systems, what constrains it.
Estimate. A rough size to decide with. Never quoted back as a plan.
Commit. Yes, no or deferred, with the approver named and what it displaces written down.

Whose signature, not how big

What it takes	Who signs
Absorbed by the team's existing capacity	Product owner
Time from another department	That department's lead, with the product owner
Money not already budgeted, or contractors	The budget holder
A commitment to a customer	Engineering review first, then the commercial owner

Four outcomes, and only four

Accepted, with an approver and a timebox.
Declined, with a written reason.
More info, naming the missing field. Twice at most.
Deferred, with a date for the next review.

What the team owes in return

An answer inside a working day. A reason for every no. No quiet deprioritisation. Showing up early to deals.

What every organisation fills in

The rules are the same everywhere. These are the blanks each organisation fills with its own names and numbers before the Portal opens:

The effective date
Who hosts the intake clinic
The product owner
Who declares a live fire, and how many are allowed per month
How fast a contract review comes back
The review cadence
Who may override
Where it is announced

The test

Is the team working on anything right now that nobody wrote down?

If it is, that work came through a side door. It has no owner on the record, and whatever it displaced was never decided.

Where GovernanceOS supports it

The Lens is where an accepted request becomes a scope. Four of the five fields have a place in it: the problem and desired outcome, the stakeholders, the success signals and the timebox. The third field, what happens if we do nothing, belongs in the problem statement.
Sign-off records who approved the scope.The people in the signature table above sign under the Lens's roles, with the budget holder as Sponsor.
The Change Forum is the only way in once work has started.
Audit Exhaust keeps every decision and override on the record, without anyone writing minutes.

The one-working-day answer and the four outcomes are the organisation's to run. GovernanceOS does not time them for you today.