Back to the single queue
Q-0013 · Escalation
Portfolio & Intake: EN1A-1013 held at commit to sprint
Pick one of the 4 options the agent set out, or return the unit to the agent with a reason.
Medium materialityOperationsEngineeringService levelOpen
Consequence
76
of a possible 100, from four factors
Rank in this queue
1st
of 15 open items held by Anika Kaplan
Records covered
1
One record, one call.
Work held behind it
240
items that cannot move until this is decided
Waiting
30 h
raised 2026-08-16 by Yuki Delgado · VP Engineering Operations
Why it is ranked where it is
Four factors, scored out of 40, 30, 20 and 10, added to 76.
The commitment it breaches
Is there a window on this, and did it close?
40 / 40
The window closed on 2026-08-16 and the item is still open.
Measured from: Point scale out of 40: a window already closed scores 40, less than a quarter of the window left scores 28, inside the window scores 14, no window at all scores 0.
The work it holds
How much is stopped behind it?
24 / 30
240 units on the same line are behind this one.
Measured from: Point scale out of 30, on the count held behind the item: 1,000 or more scores 30, 100 or more scores 24, 25 or more scores 18, 5 or more scores 12, 1 or more scores 6, nothing held scores 0.
The money at stake
What band does the record itself carry?
9 / 20
No money figure is recorded on an escalation. The band is the materiality the escalation itself carries, and the points are the points for that band. The queue does not put a dollar value on it.
Measured from: Point scale out of 20, on the materiality band: critical 20, high 15, medium 9, low 4.
Whose clock it is
Is the deadline ours, a regulator’s or a court’s?
3 / 10
The response window published on the escalation itself, in minutes, and carried on the service level for the lane it came from.
Measured from: Point scale out of 10, on whose deadline it is: statutory 10, retention 8, board or committee 6, audit 5, expiry 4, service level 3, no clock 0.
The score is carried mainly by commitment breached, which contributes 40 of the 76 points on this item. All four factors score above zero on this item.
The ranking is a scheme, not a measurement. Four factors are scored out of 40, 30, 20 and 10, and the four scores are added. The ceilings were chosen by us and no one has yet agreed them. What is measured is each factor underneath: the window and whether it closed, the count held behind the item, the band on the record and whose deadline applies.
Nothing is above this item. It is the top of Anika Kaplan’s queue.
Directly below · 76
Developer Experience: EN9A-1047 held at provision
The whole context, here
Everything the decision needs, so the queue is not a routing table.
What is being asked
Pick one of the 4 options the agent set out, or return the unit to the agent with a reason.
Why it is waiting
Request at commit to sprint valued at $58k stopped on a break condition fired. The lane cleared 72 percent of 4388 units this week without a human; this one did not clear because the evidence does not carry the decision on its own. The agent recommends: VP Engineering Operations recommends pausing the lane until the upstream data defect is fixed. Its reason: Confidence 47 percent. The comparable population is 390 units; 76 percent of them cleared on the same pattern. What separates this one is a value above the envelope.
Kind
Escalation
An agent stopped and asked for a person.
Money on the record
No figure carried
The source record carries no dollar figure. The money factor is scored from the materiality band instead.
The clock on it
Service level
Deadline
2026-08-16
Passed 21 h ago.
Whose clock
The response window published on the escalation itself, in minutes, and carried on the service level for the lane it came from.
Measurable against a recorded date.
Measured. The window is stored on the source row and the elapsed time is the difference between the time it was raised and now.
Commitment: Escalation response, 560 minutes on Portfolio & Intake
Where it came from
The queue holds no work of its own.
Escalations
/escalations · ESC-EN124
That page counts 35 waiting and places 35 items here. One record, one item, so the two counts agree.
How items are formed from that page: One item per escalation. Each one is a different unit of work at a different station.
The action that page names is: Answer an escalation an agent stopped on. Clearing this item is that same decision.
What the queue will enforce
Checked at submission, not at display.
Authority to sign
Within the cap
The register carries a grant that covers this item at this value. No grant reference is recorded against the item.
Separation of duties
No rule engaged
No separation rule is engaged on this item.
One separation rule blocks and five report. Concentrating decisions on one surface makes that difference load bearing: the queue refuses a self-raised item at the point of submission under SOD-01, and records but does not stop the other five.
Who holds it, and who covers
Anika Kaplan · Director, Security Engineering
Addressed to
Anika Kaplan
Routing is by remit alone. Nothing about the value of an item changes who receives it, only whether the person who receives it can sign it.
Cover
Morgan Idris
VP Business Services
Names business services as cover while business services is naming this post. The chain closes on itself at depth two and the automatic delegation has nowhere to send anything.
The cover board Decide it here
The outcome, the reason and the note go in one submission, and the evidence record is written on the way through.
Take the decision as asked. The item closes.
Note written onto the record
What has already been decided on this item
0 decisions on the record
Nothing has been decided on this item yet. The first submission made here will appear in this list with its evidence sequence.
Decisions already on the record were reconstructed from the source rows at assembly and carry no spine sequence. A decision taken here writes one, and the sequence is shown against it.
What this item page is, and what it is not
This page carries the whole of one decision: what is being asked, the four scores that put it where it sits, the clock that applies, the page the row still lives on, and the two rules the queue will check when the submission is made. Deciding it here is the same act as deciding it there. There is no second copy of the work.
The consequence score is ours. The four things underneath it are measured, but the ceilings that turn them into a single number out of 100 were chosen by us and have not been agreed with anyone. Read the factors, not the total, if the two ever disagree.
The authority and separation checks shown above are statements of what will happen at submission. They are enforced by the server when the form is sent, not by hiding controls on this page, so a refusal always names the rule that produced it.