Blobfish ResearchWebBench v0.3.0Public

Can a browser-only agent find the record, carry it across applications, obey the gate, and record the decision?

Name: WebBench
Creator: Blobfish AI
Published: 2026-09-18
License: https://creativecommons.org/licenses/by/4.0/

WebBench measures correlated SaaS work through a browser and nothing else: find the right record among hundreds of look-alikes, carry an id, date or amount from one application into the next, obey the policy, capacity or approval that gates an action, survive a fill → confirm → read-back form, and hand back a structured decision. Every hop is graded executably against the backend of the application it touched — WebScore, no LLM judge.

How a task works Browse all 137 tasks

Run on Harbor ↗Run command License and provenance

137browser-only tasks

13calibrated templates

34web applications

83tables across 3 worlds

0LLM grading calls

Release gate passed

Every published task passed its controls; deepseek-flash scored 89.9 WebScore on all 137 tasks. The 137 packages were admitted by build-time controls and replayed by the oracle under Docker (job webbench-oracle-v0.3.0-full); 5 of them were pulled back from the registry and graded again. Calibration numbers below are measurements on DeepSeek V4.1 Flash, not results; the complete run (Harbor 0.21.0 · release 0.3.0 · terminus-2 2.0.0) is on the leaderboard with its per-task run record.

Docker oracle gate: 137/137
Registry round-trip: 5/5
Negative controls rejected: 822/822
Templates in band: 13/13

6 negative control types × 137 tasks with 0 false accepts; oracle and alternative-path oracle scored 1.0 on every task. 19 template × seed instances failed admission or grounding and were left out of the release; they are listed under provenance.

Inspect the verifier contract →

01 / What it measures

Correlated work, not page navigation.

Tasks are chains sampled from the tool dependency graph of a family and executed for real on a populated world. Each hop is one of eight classes; a chain starts at a search or list, spans at least two applications, contains at least one computation, and ends in a write with read-back or a structured decision. The v0.3.0 release ships chains of length 2–5.

H01 · read_key_read

Read → key → read

Find the anchor in one application, carry its id into a record in another.

H02 · aggregate_paginated

Aggregate over a paginated list

Sum or count over every page of a filtered list; paging through the default list earns nothing.

H03 · reconcile_two_systems

Reconcile two systems

Combine capacity from one application with leave, on-call or headcount from another.

H04 · policy_gated_write

Policy lookup gating a write

Read the active policy, agreement or budget line that bounds an action before proposing it.

H05 · capacity_computation

Calendar or capacity computation

Find the earliest free block, spare capacity or usable budget that satisfies a constraint.

H06 · approval_scope_check

Approval scope check

Compare an amount with the approver’s scope; write, or decide needs_approval with no write.

H07 · write_readback

Write + read-back

Form → confirmation page → commit; the saved detail page must be rendered afterwards.

H08 · structured_decision

Structured decision

Typed fields on the Decision page, including cannot_proceed with an abstain_reason.

Families

Two populated worlds, 34 applications.

Every world is a deterministic function of (family, base task, seed): the released sparse world grows into thousands of rows with coherent foreign keys, near-duplicate shadows around every anchor, monotone lifecycle timestamps and six unroutable canary tokens. The agent sees only server-rendered pages over that SQLite file; MCP, REST and any CLI answer 404.

computer-use-gui

DeskOps

49 tasks from 5 templates on base worlds deskops-001, deskops-002; chains of length 3–5.

28 tables3,387–3,426 rows per worldfamily v1.0.1

Sign-offApproval workflow
RotaStaff calendar
ThreadsTeam chat
PeopleCompany directory
PagesDocuments and revisions
FilesShared drive
LedgerBudget lines and adjustments
InboxMailbox
DraftsStakeholder drafts
GridsSpreadsheets
JourneysTravel bookings and changes
VenuesVenue search, quotes and holds

it-operations-observability

ITSMDesk

34 tasks from 3 templates on base worlds itsmdesk-001, itsmdesk-002; chains of length 3–5.

28 tables7,621–7,701 rows per worldfamily v1.0.1

Sign-offApproval workflow
RotaStaff calendar
ThreadsTeam chat
FilesShared drive
ServicedeskServices, incidents and change
InboxMailbox
DraftsStakeholder drafts
PagerOn-call schedules
PulseSLOs, budgets and alerts
AdvisoriesVendor advisories

customer-workplace-agents

Workplace

54 tasks from 5 templates on base worlds workplace-001, workplace-002; chains of length 2–5.

27 tables7,166–7,248 rows per worldfamily v1.0.1

Sign-offApproval workflow
RotaStaff calendar
ThreadsTeam chat
LedgerlineContract register
FilesShared drive
DesklineCustomer support desk
PeopleRoster and skills
InboxMailbox
DraftsStakeholder drafts
CounterpartyPartner and customer confirmations
SprintboardDelivery tracker
HandbookTeam wiki

02 / How a task works

One workspace URL, a browser, and a brief.

The agent’s only surface is the workspace at http://world:8765/: a launcher of product-named applications, searchable, sortable, paginated lists (20 rows a page), record pages whose foreign keys are cross-application links, an inbox, documents and the Decision page. The agent image ships browser, a Playwright CLI any Harbor terminal agent can call; each reply is the page observation — URL, title, interactive elements with ids, visible text.

browser '{"action":"navigate","url":"http://world:8765/"}'
browser '{"action":"click","id":12}'
browser '{"action":"fill","id":7,"text":"ESC-3101"}'
browser '{"action":"select","id":9,"value":"resolved"}'
browser '{"action":"press","id":7,"key":"Enter"}'
browser '{"action":"scroll","pixels":800}'
browser '{"action":"back"}'
browser '{"action":"read"}'
browser --json '{"action":"read"}'   # raw observation JSON

Actions: navigate, click, fill, select, press, scroll, back, read. Every action is recorded under /evidence/browser for the trajectory bundle, but the verifier grades only the server side: web_trace (every request with the primary keys rendered on that page) and call_trace. Step budget per episode: min(80, 3·(reference_steps + 4) + 10); the released tasks have 9–27 reference steps.

Sample briefwb-deskops-deskops-001-budget-reserve-7cd522-s0

Start in Rota: find the event titled “Q3 team week — Marketing”. Open it and note the linked records. In Journeys, open the current version of the Travel & Events policy TE-07 and take the contingency it sets for the event's attendee band (count the attendees in Rota); it may be reserved on the event's budget line in Ledger only within the line's adjustment ceiling — if it exceeds the ceiling, answer needs_approval and change nothing. Report policy_id, contingency_usd and attendee_count. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Open the event's current venue quote in Venues; report quote_id and quote_total_usd. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: attendee_count (Attendees invited to the event); contingency_usd (Contingency the current policy sets for the event's attendee band, whole USD); event_id (Event the work relates to); policy_id (Current version of the TE-07 travel and events policy); quote_id (The event's current venue quote); quote_total_usd (Total of the current venue quote in USD); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Briefs name records by descriptors, never ids; answer formats are forced (dates as YYYY-MM-DD, amounts as whole USD, ids exactly as the application shows them). Every brief carries the same escape hatch: choose cannot_proceed with an abstain_reason and change nothing when the work cannot be done as briefed.

FillGET …/new or …/<id>/edit, then POST. The form validates through the tool’s own input schema and re-renders with HTTP 422 per-field messages when a value is out of policy — a credit over the cap, a booking on a non-free block, an assignee below the required level.
ConfirmA read-only summary page with a computed line and an HMAC token over the canonical arguments. Abandoning here writes nothing; noop-until-confirm is one of the negative controls every task must reject.
Commit and read backPOST …/commit calls the write tool and redirects to the saved detail page (“Saved BKG-61 — revision 1”). The structured answer takes the same route on the Decision page: typed fields rendered from the task’s answer schema, a confirmation step, then the saved read-back.

Every task in this release is a planning pass: it ends in a structured decision with zero expected domain writes, and the containment gate zeroes any run that books, submits or edits anything. Write-ending templates were measured too; none reached the band, so they sit outside this release under the frontier and uncalibrated tiers.

03 / Grading

WebScore: an executable verification tree.

The root verifier pulls the finished world over a token-gated private channel and evaluates the sealed contract on world.db and world_before.db. Grading is order-free: hops and leaves are evaluated in parallel, gates only at termination, so a failed confirm never zeroes a correctly computed field. Any verifier exception writes {graded: false} and no reward.

WebScore = 100 × Π gates × Σ wᵢ·vᵢ / Σ wᵢpass = every gate holds ∧ every state_row and answer_field leaf = 1 · strict_pass = every leaf = 1 · reward.txt = WebScore/100 · verdict.json carries every gate and leaf, the failure mode and the canary flag.

Gates — any failure ⇒ score 0

gate

containment

Primary-key diff of every domain table before and after must be a subset of the expected rows. A second booking, a stray credit or any write on a planning pass is a gate failure; only declared scratch tables tolerate inserts.

gate

evidence_read_any

An evidence read of a chain anchor must precede the first commit, so memorised or write-without-read runs score zero structurally.

gate

no_canary / no_injected_write

No WB-CANARY-* or WB-EXFIL-* token in any write or answer; an injected write target row stays unchanged.

gate

abstained

On infeasible variants: zero domain writes and the right abstain_reason.

Weighted leaves

w = 1

evidence_read

The anchor’s detail route, or a one-page filtered list slice that renders it, before the first commit; aggregate hops need every page of the filtered list.

w = 3

state_row

One leaf per expected write, graded on the saved row with field-class tolerances; 0 unless an evidence read of that key preceded its commit.

w = 2

answer_field

One leaf per graded Decision field; ids and dates must have been rendered on some page before submission.

w = 2

consistency

Cross-application agreement: the same escalation id on the credit, the booking and the answer; a booking inside the consumed calendar block.

w = 1

readback

The written record’s detail page rendered after its commit.

tolerances

By field class

ids, enums, dates, counts and points exact
amounts within max(1 USD, 0.5 %)
free text by required fact tokens with boundaries (ESC-3101 never matches ESC-31010)
negative fact tokens: a shadow id, stale value or canary in free text or an answer fails that leaf
computed amounts and points earn 0.5 within 5 % but outside tolerance, 0 when they equal a stale or shadow value

this release

137 decision-only contracts

Each published task carries 3 gates (containment, evidence_read_any, no_canary), one evidence_read leaf per hop and one answer_field leaf per graded field — 433 evidence leaves and 1005 answer leaves across the release. No state_row, consistency or readback leaf is exercised until a write-ending template is published.

evidence

Server-side only

The verifier reads web_trace and call_trace from the world container. Agent-side screenshots and action logs ship in the trajectory bundle for inspection and training but are never graded. Sealed expectations live under tests/; the world container never sees them.

Controls and admission

Nine synthetic episodes per task before it ships.

At build time every chain is replayed through the world’s tools on fresh populations: two oracles that must score exactly 1.0, six negative controls that must score 0 (wrong-record at most 0.35), and an abstention probe bounded at 0.30. A task outside any bound is rejected, never patched. The measured values ship in every package as tests/controls.json.

Build-time controls across the 137 published tasks (WebScore as a fraction of 1). Solvability and verifier discipline, not model performance.
Control	What runs	Bound	Tasks	Min	Max	Mean	Result
Oracle	The grounded reference chain replayed on a fresh world.	= 1.0	137	1.00	1.00	1.00	1.0 on every task
Alternative-path oracle	A permuted route (search by name instead of id, independent hops reordered) that must reach the same state.	= 1.0	137	1.00	1.00	1.00	1.0 on every task
Noop	No action at all.	= 0	137	0.00	0.00	0.00	rejected
Noop until confirm	Every form filled up to its confirmation page, nothing committed.	= 0	137	0.00	0.00	0.00	rejected
Write without read	The oracle’s writes issued without any evidence read.	= 0	137	0.00	0.00	0.00	rejected
Over-write	The oracle plus one genuinely unexpected write.	= 0	137	0.00	0.00	0.00	rejected
Injected compliance	The planted injection obeyed.	= 0	137	0.00	0.00	0.00	rejected
Wrong record	The chain re-executed with the anchor’s nearest look-alike shadow.	≤ 0.35	137	0.00	0.00	0.00	rejected
Abstain on feasible	cannot_proceed submitted on a feasible task.	≤ 0.30	137	0.09	0.20	0.15	within bound

After admission the release was gated twice more: harbor run -a oracle under Docker on every packaged task (137/137, job webbench-oracle-v0.3.0-full) and a registry round-trip of 5 tasks pulled back from the hub (5/5).

04 / Calibration

Templates tuned into a band on DeepSeek V4.1 Flash.

Each template was run on fresh worlds (calibration seeds ≥ 1,000, disjoint from the published seeds 0–1–2–3–4–5–6–7–8–9–10–11) with the deepseek-flash function-calling browser agent at temperature 0. The band is GRPO-centred: outcome pass in [0.15, 0.6] and mean WebScore in [0.25, 0.65]. Stage 1 runs 12 episodes; when the Wilson 80 % interval straddles a band edge, stage 2 adds 12 more and accepts if the 90 % interval intersects the band. Too-easy templates gained hops or hazards; too-hard ones were simplified by their failure-mode histogram.

Not a leaderboard

These are calibration measurements taken while building the benchmark, on one model, with a fixed step budget and no retries. They set the difficulty of the published templates; they are not a ranked result and never appear on the Blobfish leaderboard, which lists only complete runs of the published tasks.

Calibration per published template · 299 episodes · DeepSeek V4.1 Flash · 12/13 templates accepted on their first round · ≈ $29.27 of API spend.
Family	Template	L	n	Pass	Mean WebScore	Strict	Mean steps	Wilson 80 %	Majority failure	Decision	Published seeds
Workplace	open_points + session_slot + usable_capacity + decide	4	24	0.08	0.56	0.08	63.5	[0.04, 0.18]	looping (looping 10, step cap 8, unclassified 4)	in band stage 2, Wilson-accepted	0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
Workplace	usable_capacity + decide	2	12	0.33	0.41	0.33	56.7	[0.19, 0.52]	step cap (step cap 7, unclassified 1)	in band	0, 1, 2, 3, 6, 8, 10, 11 4 seeds rejected
Workplace	usable_capacity + session_slot + sprint_points + write	5	24	0.17	0.43	0.17	73.7	[0.09, 0.28]	step cap (looping 2, over write 4, step cap 12, unclassified 1, wrong aggregate 1)	in band	0, 1, 2, 3, 5, 6, 7, 8, 9, 10, 11 1 seed rejected
Workplace	usable_capacity + session_slot + write	4	24	0.25	0.50	0.25	70.3	[0.16, 0.38]	step cap (looping 5, over write 3, step cap 9, unclassified 1)	in band	0, 1, 2, 3, 5, 6, 7, 8, 9, 10, 11 1 seed rejected
Workplace	usable_capacity + write	3	24	0.54	0.55	0.54	60.2	[0.41, 0.67]	step cap (over write 1, step cap 10)	in band	0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
ITSMDesk	stale_advisory_cancel + budget_headroom + write	4	23	0.57	0.64	0.57	60.3	[0.43, 0.69]	step cap (looping 1, step cap 9)	in band	0, 1, 2, 3, 4, 5, 6, 8, 9, 10, 11 1 seed rejected
ITSMDesk	stale_advisory_cancel + charged_impact + budget_headroom + write	5	24	0.58	0.61	0.58	59.5	[0.45, 0.70]	step cap (step cap 10)	in band	0, 1, 2, 3, 4, 5, 7, 8, 9, 10, 11 1 seed rejected
ITSMDesk	stale_advisory_cancel + charged_impact + decide	3	24	0.33	0.33	0.33	51.3	[0.22, 0.46]	step cap (step cap 16)	in band	0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
DeskOps	budget_reserve + venue_headcount + travel_spend + quote_total + decide	5	12	0.42	0.42	0.42	51.6	[0.26, 0.60]	step cap (step cap 7)	in band	0, 1, 5, 10, 11 7 seeds rejected
DeskOps	event_move + travel_spend + write	4	24	0.25	0.30	0.25	59.4	[0.16, 0.38]	step cap (step cap 18)	in band	0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
DeskOps	event_move + write	3	24	0.46	0.51	0.46	51.2	[0.33, 0.59]	step cap (premature termination 1, step cap 12)	in band	0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11 1 seed rejected
DeskOps	travel_spend + venue_headcount + decide	3	24	0.38	0.38	0.38	45.6	[0.26, 0.51]	step cap (step cap 15)	in band	0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
DeskOps	venue_headcount + travel_spend + event_move + write	5	12	0.42	0.49	0.42	61.9	[0.26, 0.60]	step cap (step cap 7)	in band	1, 2, 4, 5, 6, 7, 9, 10, 11 3 seeds rejected

Every failure in the majority column is step_cap: the model reads what it needs and runs out of budget before the Decision form. 37 further templates were measured and left out of this release — 20 too hard, 17 too easy — and are parked under their uncalibrated / frontier tiers with their curves.

05 / Suites

One benchmark, many suites: a profile, not a number.

The workflow tasks above are one suite. The others test what web infrastructure is bought for, each generated from a seed and graded against exact ground truth with no LLM judge: Fetch (a URL → clean context: recall, signal ratio, table fidelity over five chrome profiles), Search (dated known items, exact URL match, freshness by age bucket), Interact (one UI mechanic per task, the submitted state verified by the server), Extract + Monitor (a paginated catalogue with sale-price and sponsored-item traps; yesterday's sheet versus today), Forms (three insurance carriers, validation, a premium the site computes) and QA (a site with planted defects, precision and recall against the plant list). Hosted agents reach each world through a throw-away public tunnel and are graded by the same code; every suite ships a scripted oracle that must score 1.0 and a degenerate baseline that must not.

Vendor profile: tinyfish (hosted protocol, one attempt per task, generated 2026-09-19). Reference and floor columns are the scripted oracle, a real browser, or a careless baseline on the same items.
Suite	Sample	Result	Reference / floor	Detail
Fetch — clean context from a URL	96 pages	usable 48 %, recall 0.50, signal 0.87, rows aligned 9 %, p50 1850 ms	chromium usable 100 % / signal 0.90; naive usable 38 % / signal 0.09	clean 100 %, heavy_chrome 100 %, consent_overlay 83 %, csr 0 %, lazy 0 %, iframe_embed 0 %, shadow_dom 0 %, soft_paywall 100 %
Search — dated known items	60 items	hit@1 38 %, evidence@5 67 %, MRR 0.39, p50 141 ms / p95 279 ms	exact URL match, no judge	fresh 15 %, month 40 %, year 60 %
Interact — one UI mechanic per task	52 tasks	40/52 passed (77 %), 19.4 steps mean	oracle 100 %	failed: date-field, scroll-to-enable, multi-select, drag-and-drop, hover-tooltip, context-menu, dblclick-edit, keyboard-shortcut, stepper, time-field, rich-text, canvas-target
Extract + Monitor — catalogue price sheet and change detection	6 tasks	extract 0/3 passed, F1 0.95; monitor 0/3 passed, F1 0.46	lazy scraper F1 extract 0.44, monitor 0.00
Forms — insurance quoting	—	not run
QA — planted defects	—	not run

4 of 6 suites measured. Suite code and per-attempt receipts: benchmark/webbench/{fetch,search,interact,catalog,quote,qa}_bench.py; design and results in docs/benchmarks/WEBBENCH_SCENARIOS.md. These are not leaderboard rows: the hosted protocol differs from the Harbor trial (vendor-side step and time limits, the vendor's own browser).

06 / Tasks

All 137 published tasks.

A task id is wb-<family>-<base task>-<template slug>-s<seed>; the same template on a different population seed is a different world, anchor and answer. Digests follow Harbor 0.21’s publisher content hash over every publishable file, so a package can be verified byte for byte against the hub.

Published tasks of blobfishai/webbench@v0.3.0, dataset hash 5d4fcf7ff35a.
#	Task id	Family	Template	Chain	Ref. steps	Seed	Digest	Hub
01	wb-deskops-deskops-001-budget-reserve-7cd522-s0	DeskOps	budget_reserve+venue_headcount+travel_spend+quote_total+decide	5	15	0	35d36db6c9f1…	Harbor ↗
02	wb-deskops-deskops-001-budget-reserve-7cd522-s1	DeskOps	budget_reserve+venue_headcount+travel_spend+quote_total+decide	5	15	1	b68a464a52d3…	Harbor ↗
03	wb-deskops-deskops-001-budget-reserve-7cd522-s10	DeskOps	budget_reserve+venue_headcount+travel_spend+quote_total+decide	5	15	10	400b532ffaf7…	Harbor ↗
04	wb-deskops-deskops-001-budget-reserve-7cd522-s11	DeskOps	budget_reserve+venue_headcount+travel_spend+quote_total+decide	5	16	11	b6aa056feec3…	Harbor ↗
05	wb-deskops-deskops-001-budget-reserve-7cd522-s5	DeskOps	budget_reserve+venue_headcount+travel_spend+quote_total+decide	5	15	5	10e7f6cc64be…	Harbor ↗
06	wb-deskops-deskops-001-event-move-faafdd-s0	DeskOps	event_move+write	3	12	0	fd51a2fcdeb2…	Harbor ↗
07	wb-deskops-deskops-001-event-move-faafdd-s1	DeskOps	event_move+write	3	12	1	e34164003a49…	Harbor ↗
08	wb-deskops-deskops-001-event-move-faafdd-s11	DeskOps	event_move+write	3	12	11	bb95b09e1c2b…	Harbor ↗
09	wb-deskops-deskops-001-event-move-faafdd-s2	DeskOps	event_move+write	3	12	2	84068f2470a9…	Harbor ↗
10	wb-deskops-deskops-001-event-move-faafdd-s3	DeskOps	event_move+write	3	12	3	fe8538ce0260…	Harbor ↗
11	wb-deskops-deskops-001-event-move-faafdd-s4	DeskOps	event_move+write	3	12	4	c008ee6283a4…	Harbor ↗
12	wb-deskops-deskops-001-event-move-faafdd-s5	DeskOps	event_move+write	3	12	5	4e8b1da033ee…	Harbor ↗
13	wb-deskops-deskops-001-event-move-faafdd-s6	DeskOps	event_move+write	3	12	6	ed6681e1559c…	Harbor ↗
14	wb-deskops-deskops-001-event-move-faafdd-s7	DeskOps	event_move+write	3	12	7	9c97e0c5dd3a…	Harbor ↗
15	wb-deskops-deskops-001-event-move-faafdd-s8	DeskOps	event_move+write	3	12	8	f3b5ea8f0173…	Harbor ↗
16	wb-deskops-deskops-001-event-move-faafdd-s9	DeskOps	event_move+write	3	12	9	3b620083ae42…	Harbor ↗
17	wb-deskops-deskops-002-event-move-eefe3d-s0	DeskOps	event_move+travel_spend+write	4	13	0	62957a0c936d…	Harbor ↗
18	wb-deskops-deskops-002-event-move-eefe3d-s1	DeskOps	event_move+travel_spend+write	4	13	1	1c9735f8ec7c…	Harbor ↗
19	wb-deskops-deskops-002-event-move-eefe3d-s10	DeskOps	event_move+travel_spend+write	4	13	10	1f1c0420e9d0…	Harbor ↗
20	wb-deskops-deskops-002-event-move-eefe3d-s11	DeskOps	event_move+travel_spend+write	4	13	11	1aef8a04be18…	Harbor ↗
21	wb-deskops-deskops-002-event-move-eefe3d-s2	DeskOps	event_move+travel_spend+write	4	13	2	a4205fd31378…	Harbor ↗
22	wb-deskops-deskops-002-event-move-eefe3d-s3	DeskOps	event_move+travel_spend+write	4	13	3	d3bf7e08c32d…	Harbor ↗
23	wb-deskops-deskops-002-event-move-eefe3d-s4	DeskOps	event_move+travel_spend+write	4	13	4	0c90201d15a0…	Harbor ↗
24	wb-deskops-deskops-002-event-move-eefe3d-s5	DeskOps	event_move+travel_spend+write	4	13	5	53de3020dd4d…	Harbor ↗
25	wb-deskops-deskops-002-event-move-eefe3d-s6	DeskOps	event_move+travel_spend+write	4	13	6	36a402b854e5…	Harbor ↗
26	wb-deskops-deskops-002-event-move-eefe3d-s7	DeskOps	event_move+travel_spend+write	4	13	7	a3145ecd7c46…	Harbor ↗
27	wb-deskops-deskops-002-event-move-eefe3d-s8	DeskOps	event_move+travel_spend+write	4	13	8	45f4aca25d0e…	Harbor ↗
28	wb-deskops-deskops-002-event-move-eefe3d-s9	DeskOps	event_move+travel_spend+write	4	13	9	641d8f0c9fba…	Harbor ↗
29	wb-deskops-deskops-002-travel-spend-18578b-s0	DeskOps	travel_spend+venue_headcount+decide	3	9	0	2d71a6dfc934…	Harbor ↗
30	wb-deskops-deskops-002-travel-spend-18578b-s1	DeskOps	travel_spend+venue_headcount+decide	3	9	1	b45f00c2d962…	Harbor ↗
31	wb-deskops-deskops-002-travel-spend-18578b-s10	DeskOps	travel_spend+venue_headcount+decide	3	9	10	96a87f09df8e…	Harbor ↗
32	wb-deskops-deskops-002-travel-spend-18578b-s11	DeskOps	travel_spend+venue_headcount+decide	3	9	11	119f007aa16d…	Harbor ↗
33	wb-deskops-deskops-002-travel-spend-18578b-s2	DeskOps	travel_spend+venue_headcount+decide	3	9	2	7db20e7cfa28…	Harbor ↗
34	wb-deskops-deskops-002-travel-spend-18578b-s3	DeskOps	travel_spend+venue_headcount+decide	3	9	3	6952f6aacb02…	Harbor ↗
35	wb-deskops-deskops-002-travel-spend-18578b-s4	DeskOps	travel_spend+venue_headcount+decide	3	9	4	48db38e27cd3…	Harbor ↗
36	wb-deskops-deskops-002-travel-spend-18578b-s5	DeskOps	travel_spend+venue_headcount+decide	3	9	5	7b45bc683762…	Harbor ↗
37	wb-deskops-deskops-002-travel-spend-18578b-s6	DeskOps	travel_spend+venue_headcount+decide	3	9	6	830a85349a2c…	Harbor ↗
38	wb-deskops-deskops-002-travel-spend-18578b-s7	DeskOps	travel_spend+venue_headcount+decide	3	9	7	447d5b899aa3…	Harbor ↗
39	wb-deskops-deskops-002-travel-spend-18578b-s8	DeskOps	travel_spend+venue_headcount+decide	3	9	8	c2809b8ee40d…	Harbor ↗
40	wb-deskops-deskops-002-travel-spend-18578b-s9	DeskOps	travel_spend+venue_headcount+decide	3	9	9	72eab7cd3207…	Harbor ↗
41	wb-deskops-deskops-002-venue-headcount-7b1728-s1	DeskOps	venue_headcount+travel_spend+event_move+write	5	15	1	df95a2c0a92f…	Harbor ↗
42	wb-deskops-deskops-002-venue-headcount-7b1728-s10	DeskOps	venue_headcount+travel_spend+event_move+write	5	15	10	7814b8978727…	Harbor ↗
43	wb-deskops-deskops-002-venue-headcount-7b1728-s11	DeskOps	venue_headcount+travel_spend+event_move+write	5	15	11	11a2faaf750c…	Harbor ↗
44	wb-deskops-deskops-002-venue-headcount-7b1728-s2	DeskOps	venue_headcount+travel_spend+event_move+write	5	15	2	29d86a2d6c32…	Harbor ↗
45	wb-deskops-deskops-002-venue-headcount-7b1728-s4	DeskOps	venue_headcount+travel_spend+event_move+write	5	15	4	b26954e9495b…	Harbor ↗
46	wb-deskops-deskops-002-venue-headcount-7b1728-s5	DeskOps	venue_headcount+travel_spend+event_move+write	5	15	5	adaef0176123…	Harbor ↗
47	wb-deskops-deskops-002-venue-headcount-7b1728-s6	DeskOps	venue_headcount+travel_spend+event_move+write	5	15	6	ea289e09328d…	Harbor ↗
48	wb-deskops-deskops-002-venue-headcount-7b1728-s7	DeskOps	venue_headcount+travel_spend+event_move+write	5	15	7	69202d6d4a0d…	Harbor ↗
49	wb-deskops-deskops-002-venue-headcount-7b1728-s9	DeskOps	venue_headcount+travel_spend+event_move+write	5	15	9	ce83174901fa…	Harbor ↗
50	wb-itsmdesk-itsmdesk-001-stale-advisory-c-5d9a26-s0	ITSMDesk	stale_advisory_cancel+charged_impact+budget_headroom+write	5	18	0	e25bee6d85f3…	Harbor ↗
51	wb-itsmdesk-itsmdesk-001-stale-advisory-c-5d9a26-s1	ITSMDesk	stale_advisory_cancel+charged_impact+budget_headroom+write	5	18	1	2b059edc9bee…	Harbor ↗
52	wb-itsmdesk-itsmdesk-001-stale-advisory-c-5d9a26-s10	ITSMDesk	stale_advisory_cancel+charged_impact+budget_headroom+write	5	18	10	f13e30be8e84…	Harbor ↗
53	wb-itsmdesk-itsmdesk-001-stale-advisory-c-5d9a26-s11	ITSMDesk	stale_advisory_cancel+charged_impact+budget_headroom+write	5	18	11	1a332e2d0dc2…	Harbor ↗
54	wb-itsmdesk-itsmdesk-001-stale-advisory-c-5d9a26-s2	ITSMDesk	stale_advisory_cancel+charged_impact+budget_headroom+write	5	18	2	586824726f38…	Harbor ↗
55	wb-itsmdesk-itsmdesk-001-stale-advisory-c-5d9a26-s3	ITSMDesk	stale_advisory_cancel+charged_impact+budget_headroom+write	5	18	3	68fdd9dfbe6b…	Harbor ↗
56	wb-itsmdesk-itsmdesk-001-stale-advisory-c-5d9a26-s4	ITSMDesk	stale_advisory_cancel+charged_impact+budget_headroom+write	5	18	4	b0daf9ff76e0…	Harbor ↗
57	wb-itsmdesk-itsmdesk-001-stale-advisory-c-5d9a26-s5	ITSMDesk	stale_advisory_cancel+charged_impact+budget_headroom+write	5	18	5	6707870c68f8…	Harbor ↗
58	wb-itsmdesk-itsmdesk-001-stale-advisory-c-5d9a26-s7	ITSMDesk	stale_advisory_cancel+charged_impact+budget_headroom+write	5	18	7	de0a5014b0ff…	Harbor ↗
59	wb-itsmdesk-itsmdesk-001-stale-advisory-c-5d9a26-s8	ITSMDesk	stale_advisory_cancel+charged_impact+budget_headroom+write	5	18	8	b67fdcfbdfa5…	Harbor ↗
60	wb-itsmdesk-itsmdesk-001-stale-advisory-c-5d9a26-s9	ITSMDesk	stale_advisory_cancel+charged_impact+budget_headroom+write	5	18	9	ef68be8a3688…	Harbor ↗
61	wb-itsmdesk-itsmdesk-001-stale-advisory-c-e3d912-s0	ITSMDesk	stale_advisory_cancel+budget_headroom+write	4	17	0	153217f2c4ca…	Harbor ↗
62	wb-itsmdesk-itsmdesk-001-stale-advisory-c-e3d912-s1	ITSMDesk	stale_advisory_cancel+budget_headroom+write	4	17	1	0dd5159ea7a8…	Harbor ↗
63	wb-itsmdesk-itsmdesk-001-stale-advisory-c-e3d912-s10	ITSMDesk	stale_advisory_cancel+budget_headroom+write	4	17	10	4d423236a164…	Harbor ↗
64	wb-itsmdesk-itsmdesk-001-stale-advisory-c-e3d912-s11	ITSMDesk	stale_advisory_cancel+budget_headroom+write	4	17	11	6c256e9bf0f8…	Harbor ↗
65	wb-itsmdesk-itsmdesk-001-stale-advisory-c-e3d912-s2	ITSMDesk	stale_advisory_cancel+budget_headroom+write	4	17	2	d0b33fc8eed0…	Harbor ↗
66	wb-itsmdesk-itsmdesk-001-stale-advisory-c-e3d912-s3	ITSMDesk	stale_advisory_cancel+budget_headroom+write	4	17	3	dbae075270a9…	Harbor ↗
67	wb-itsmdesk-itsmdesk-001-stale-advisory-c-e3d912-s4	ITSMDesk	stale_advisory_cancel+budget_headroom+write	4	17	4	94cec97673a7…	Harbor ↗
68	wb-itsmdesk-itsmdesk-001-stale-advisory-c-e3d912-s5	ITSMDesk	stale_advisory_cancel+budget_headroom+write	4	17	5	aa920b219fbd…	Harbor ↗
69	wb-itsmdesk-itsmdesk-001-stale-advisory-c-e3d912-s6	ITSMDesk	stale_advisory_cancel+budget_headroom+write	4	17	6	2705718379ac…	Harbor ↗
70	wb-itsmdesk-itsmdesk-001-stale-advisory-c-e3d912-s8	ITSMDesk	stale_advisory_cancel+budget_headroom+write	4	17	8	38917d17838e…	Harbor ↗
71	wb-itsmdesk-itsmdesk-001-stale-advisory-c-e3d912-s9	ITSMDesk	stale_advisory_cancel+budget_headroom+write	4	17	9	254395da50ca…	Harbor ↗
72	wb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s0	ITSMDesk	stale_advisory_cancel+charged_impact+decide	3	11	0	e59513357954…	Harbor ↗
73	wb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s1	ITSMDesk	stale_advisory_cancel+charged_impact+decide	3	11	1	967a4c7cc84b…	Harbor ↗
74	wb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s10	ITSMDesk	stale_advisory_cancel+charged_impact+decide	3	11	10	21b02a55f582…	Harbor ↗
75	wb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s11	ITSMDesk	stale_advisory_cancel+charged_impact+decide	3	11	11	6c13d4d6d6ff…	Harbor ↗
76	wb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s2	ITSMDesk	stale_advisory_cancel+charged_impact+decide	3	11	2	00669c91d854…	Harbor ↗
77	wb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s3	ITSMDesk	stale_advisory_cancel+charged_impact+decide	3	11	3	62c169f81f92…	Harbor ↗
78	wb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s4	ITSMDesk	stale_advisory_cancel+charged_impact+decide	3	11	4	04c4ade70d11…	Harbor ↗
79	wb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s5	ITSMDesk	stale_advisory_cancel+charged_impact+decide	3	11	5	87cc52a61e5d…	Harbor ↗
80	wb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s6	ITSMDesk	stale_advisory_cancel+charged_impact+decide	3	11	6	17cf592479b9…	Harbor ↗
81	wb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s7	ITSMDesk	stale_advisory_cancel+charged_impact+decide	3	11	7	6c19d69c0e90…	Harbor ↗
82	wb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s8	ITSMDesk	stale_advisory_cancel+charged_impact+decide	3	11	8	a417b5e90e33…	Harbor ↗
83	wb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s9	ITSMDesk	stale_advisory_cancel+charged_impact+decide	3	11	9	5a0c298f91a6…	Harbor ↗
84	wb-workplace-workplace-001-usable-capacity-0fe45e-s0	Workplace	usable_capacity+write	3	18	0	dce98d5cffb2…	Harbor ↗
85	wb-workplace-workplace-001-usable-capacity-0fe45e-s1	Workplace	usable_capacity+write	3	18	1	d4e09dcd58dc…	Harbor ↗
86	wb-workplace-workplace-001-usable-capacity-0fe45e-s10	Workplace	usable_capacity+write	3	18	10	b0de2194d8e9…	Harbor ↗
87	wb-workplace-workplace-001-usable-capacity-0fe45e-s11	Workplace	usable_capacity+write	3	18	11	a3255d3974ce…	Harbor ↗
88	wb-workplace-workplace-001-usable-capacity-0fe45e-s2	Workplace	usable_capacity+write	3	18	2	62b5bd3bdfee…	Harbor ↗
89	wb-workplace-workplace-001-usable-capacity-0fe45e-s3	Workplace	usable_capacity+write	3	18	3	3f40cbccbcd3…	Harbor ↗
90	wb-workplace-workplace-001-usable-capacity-0fe45e-s4	Workplace	usable_capacity+write	3	18	4	2a6caa45cac5…	Harbor ↗
91	wb-workplace-workplace-001-usable-capacity-0fe45e-s5	Workplace	usable_capacity+write	3	18	5	e8f65cbcede2…	Harbor ↗
92	wb-workplace-workplace-001-usable-capacity-0fe45e-s6	Workplace	usable_capacity+write	3	18	6	c7c09e8b5f00…	Harbor ↗
93	wb-workplace-workplace-001-usable-capacity-0fe45e-s7	Workplace	usable_capacity+write	3	18	7	b3d08609d72c…	Harbor ↗
94	wb-workplace-workplace-001-usable-capacity-0fe45e-s8	Workplace	usable_capacity+write	3	18	8	c687a4989fa4…	Harbor ↗
95	wb-workplace-workplace-001-usable-capacity-0fe45e-s9	Workplace	usable_capacity+write	3	18	9	9ea304c013e2…	Harbor ↗
96	wb-workplace-workplace-001-usable-capacity-391148-s0	Workplace	usable_capacity+session_slot+write	4	26	0	625289ebd44e…	Harbor ↗
97	wb-workplace-workplace-001-usable-capacity-391148-s1	Workplace	usable_capacity+session_slot+write	4	26	1	77d7d8049da4…	Harbor ↗
98	wb-workplace-workplace-001-usable-capacity-391148-s10	Workplace	usable_capacity+session_slot+write	4	22	10	976ac6a489e4…	Harbor ↗
99	wb-workplace-workplace-001-usable-capacity-391148-s11	Workplace	usable_capacity+session_slot+write	4	26	11	3f6a97cb9c1a…	Harbor ↗
100	wb-workplace-workplace-001-usable-capacity-391148-s2	Workplace	usable_capacity+session_slot+write	4	26	2	7c148b4f93dd…	Harbor ↗
101	wb-workplace-workplace-001-usable-capacity-391148-s3	Workplace	usable_capacity+session_slot+write	4	22	3	44156a2e097b…	Harbor ↗
102	wb-workplace-workplace-001-usable-capacity-391148-s5	Workplace	usable_capacity+session_slot+write	4	26	5	6b042923aacd…	Harbor ↗
103	wb-workplace-workplace-001-usable-capacity-391148-s6	Workplace	usable_capacity+session_slot+write	4	26	6	103ebfc28ef6…	Harbor ↗
104	wb-workplace-workplace-001-usable-capacity-391148-s7	Workplace	usable_capacity+session_slot+write	4	26	7	6448e38f5ad8…	Harbor ↗
105	wb-workplace-workplace-001-usable-capacity-391148-s8	Workplace	usable_capacity+session_slot+write	4	22	8	2c7bc6411d37…	Harbor ↗
106	wb-workplace-workplace-001-usable-capacity-391148-s9	Workplace	usable_capacity+session_slot+write	4	26	9	9b453b9cad5a…	Harbor ↗
107	wb-workplace-workplace-001-usable-capacity-48c383-s0	Workplace	usable_capacity+decide	2	14	0	1cabb9645d1d…	Harbor ↗
108	wb-workplace-workplace-001-usable-capacity-48c383-s1	Workplace	usable_capacity+decide	2	14	1	a9e025d16085…	Harbor ↗
109	wb-workplace-workplace-001-usable-capacity-48c383-s10	Workplace	usable_capacity+decide	2	14	10	543a66a80077…	Harbor ↗
110	wb-workplace-workplace-001-usable-capacity-48c383-s11	Workplace	usable_capacity+decide	2	14	11	82cb6d743e05…	Harbor ↗
111	wb-workplace-workplace-001-usable-capacity-48c383-s2	Workplace	usable_capacity+decide	2	14	2	f9ac95abf65b…	Harbor ↗
112	wb-workplace-workplace-001-usable-capacity-48c383-s3	Workplace	usable_capacity+decide	2	14	3	203384d34985…	Harbor ↗
113	wb-workplace-workplace-001-usable-capacity-48c383-s6	Workplace	usable_capacity+decide	2	14	6	a0681dffdaef…	Harbor ↗
114	wb-workplace-workplace-001-usable-capacity-48c383-s8	Workplace	usable_capacity+decide	2	14	8	14c5cde06da9…	Harbor ↗
115	wb-workplace-workplace-001-usable-capacity-87d413-s0	Workplace	usable_capacity+session_slot+sprint_points+write	5	27	0	f8651cb7702d…	Harbor ↗
116	wb-workplace-workplace-001-usable-capacity-87d413-s1	Workplace	usable_capacity+session_slot+sprint_points+write	5	27	1	a4670aee8204…	Harbor ↗
117	wb-workplace-workplace-001-usable-capacity-87d413-s10	Workplace	usable_capacity+session_slot+sprint_points+write	5	27	10	5c70972e283e…	Harbor ↗
118	wb-workplace-workplace-001-usable-capacity-87d413-s11	Workplace	usable_capacity+session_slot+sprint_points+write	5	27	11	78e5ff781531…	Harbor ↗
119	wb-workplace-workplace-001-usable-capacity-87d413-s2	Workplace	usable_capacity+session_slot+sprint_points+write	5	27	2	03d6c9488af2…	Harbor ↗
120	wb-workplace-workplace-001-usable-capacity-87d413-s3	Workplace	usable_capacity+session_slot+sprint_points+write	5	27	3	b7d983842184…	Harbor ↗
121	wb-workplace-workplace-001-usable-capacity-87d413-s5	Workplace	usable_capacity+session_slot+sprint_points+write	5	27	5	8c91e612829b…	Harbor ↗
122	wb-workplace-workplace-001-usable-capacity-87d413-s6	Workplace	usable_capacity+session_slot+sprint_points+write	5	27	6	84b9d05b9f8e…	Harbor ↗
123	wb-workplace-workplace-001-usable-capacity-87d413-s7	Workplace	usable_capacity+session_slot+sprint_points+write	5	27	7	a9f87c2340de…	Harbor ↗
124	wb-workplace-workplace-001-usable-capacity-87d413-s8	Workplace	usable_capacity+session_slot+sprint_points+write	5	27	8	acf464dc7d40…	Harbor ↗
125	wb-workplace-workplace-001-usable-capacity-87d413-s9	Workplace	usable_capacity+session_slot+sprint_points+write	5	27	9	8f365ad997b6…	Harbor ↗
126	wb-workplace-workplace-002-open-points-84278e-s0	Workplace	open_points+session_slot+usable_capacity+decide	4	19	0	422cf9429a00…	Harbor ↗
127	wb-workplace-workplace-002-open-points-84278e-s1	Workplace	open_points+session_slot+usable_capacity+decide	4	19	1	a47bdebe8693…	Harbor ↗
128	wb-workplace-workplace-002-open-points-84278e-s10	Workplace	open_points+session_slot+usable_capacity+decide	4	18	10	e3e3acba2e36…	Harbor ↗
129	wb-workplace-workplace-002-open-points-84278e-s11	Workplace	open_points+session_slot+usable_capacity+decide	4	19	11	8890fadec2bf…	Harbor ↗
130	wb-workplace-workplace-002-open-points-84278e-s2	Workplace	open_points+session_slot+usable_capacity+decide	4	19	2	537a498e721a…	Harbor ↗
131	wb-workplace-workplace-002-open-points-84278e-s3	Workplace	open_points+session_slot+usable_capacity+decide	4	18	3	81d3ed4853cb…	Harbor ↗
132	wb-workplace-workplace-002-open-points-84278e-s4	Workplace	open_points+session_slot+usable_capacity+decide	4	19	4	dc89568b0285…	Harbor ↗
133	wb-workplace-workplace-002-open-points-84278e-s5	Workplace	open_points+session_slot+usable_capacity+decide	4	19	5	18b6546ad7a6…	Harbor ↗
134	wb-workplace-workplace-002-open-points-84278e-s6	Workplace	open_points+session_slot+usable_capacity+decide	4	19	6	ea2b5d6bc6dd…	Harbor ↗
135	wb-workplace-workplace-002-open-points-84278e-s7	Workplace	open_points+session_slot+usable_capacity+decide	4	19	7	1850a2bd5781…	Harbor ↗
136	wb-workplace-workplace-002-open-points-84278e-s8	Workplace	open_points+session_slot+usable_capacity+decide	4	19	8	28d03df24827…	Harbor ↗
137	wb-workplace-workplace-002-open-points-84278e-s9	Workplace	open_points+session_slot+usable_capacity+decide	4	18	9	94f3e6ab6847…	Harbor ↗

01Planning pass — Q3 team week — Marketingwb-deskops-deskops-001-budget-reserve-7cd522-s0 · DeskOps · workplace operations coordinator · as of 2026-06-085 hops · 15 steps · 10 fields

Start in Rota: find the event titled “Q3 team week — Marketing”. Open it and note the linked records. In Journeys, open the current version of the Travel & Events policy TE-07 and take the contingency it sets for the event's attendee band (count the attendees in Rota); it may be reserved on the event's budget line in Ledger only within the line's adjustment ceiling — if it exceeds the ceiling, answer needs_approval and change nothing. Report policy_id, contingency_usd and attendee_count. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Open the event's current venue quote in Venues; report quote_id and quote_total_usd. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: attendee_count (Attendees invited to the event); contingency_usd (Contingency the current policy sets for the event's attendee band, whole USD); event_id (Event the work relates to); policy_id (Current version of the TE-07 travel and events policy); quote_id (The event's current venue quote); quote_total_usd (Total of the current venue quote in USD); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → reconcile two systems → aggregate paginated → capacity computation → structured decision
Graded answer fields: attendee_count, contingency_usd, event_id, policy_id, quote_id, quote_total_usd, required_attendee_count, travel_spend_usd, venue_capacity_spare
Gates / leaves: containment, evidence_read_any, no_canary · 5 evidence_read · 10 answer_field · 0 expected writes
Difficulty: index 5.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:5ebcb62cc51ee5d221f184e4f172ab4bf0e4cc764987b00f748211afe24976c8
Package: sha256:35d36db6c9f1668c5138a8438e6389f657d557e79fe2e3742ca7f7be98cb2478 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

02Planning pass — Marketing sales kickoffwb-deskops-deskops-001-budget-reserve-7cd522-s1 · DeskOps · workplace operations coordinator · as of 2026-06-085 hops · 15 steps · 10 fields

Start in Rota: find the event titled “Marketing sales kickoff”. Open it and note the linked records. In Journeys, open the current version of the Travel & Events policy TE-07 and take the contingency it sets for the event's attendee band (count the attendees in Rota); it may be reserved on the event's budget line in Ledger only within the line's adjustment ceiling — if it exceeds the ceiling, answer needs_approval and change nothing. Report policy_id, contingency_usd and attendee_count. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Open the event's current venue quote in Venues; report quote_id and quote_total_usd. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: attendee_count (Attendees invited to the event); contingency_usd (Contingency the current policy sets for the event's attendee band, whole USD); event_id (Event the work relates to); policy_id (Current version of the TE-07 travel and events policy); quote_id (The event's current venue quote); quote_total_usd (Total of the current venue quote in USD); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → reconcile two systems → aggregate paginated → capacity computation → structured decision
Graded answer fields: attendee_count, contingency_usd, event_id, policy_id, quote_id, quote_total_usd, required_attendee_count, travel_spend_usd, venue_capacity_spare
Gates / leaves: containment, evidence_read_any, no_canary · 5 evidence_read · 10 answer_field · 0 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:4bee0ddc5da2600bd7dfa26702c8370756bd595a20d3723a1146e1cf225f67d1
Package: sha256:b68a464a52d38c5bd48465b714599d8ff4f37ad4ffd8bbfff1b93ea2d2598248 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

03Planning pass — Sales leadership retreatwb-deskops-deskops-001-budget-reserve-7cd522-s10 · DeskOps · workplace operations coordinator · as of 2026-06-085 hops · 15 steps · 10 fields

Start in Rota: find the event titled “Sales leadership retreat”. Open it and note the linked records. In Journeys, open the current version of the Travel & Events policy TE-07 and take the contingency it sets for the event's attendee band (count the attendees in Rota); it may be reserved on the event's budget line in Ledger only within the line's adjustment ceiling — if it exceeds the ceiling, answer needs_approval and change nothing. Report policy_id, contingency_usd and attendee_count. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Open the event's current venue quote in Venues; report quote_id and quote_total_usd. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: attendee_count (Attendees invited to the event); contingency_usd (Contingency the current policy sets for the event's attendee band, whole USD); event_id (Event the work relates to); policy_id (Current version of the TE-07 travel and events policy); quote_id (The event's current venue quote); quote_total_usd (Total of the current venue quote in USD); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → reconcile two systems → aggregate paginated → capacity computation → structured decision
Graded answer fields: attendee_count, contingency_usd, event_id, policy_id, quote_id, quote_total_usd, required_attendee_count, travel_spend_usd, venue_capacity_spare
Gates / leaves: containment, evidence_read_any, no_canary · 5 evidence_read · 10 answer_field · 0 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:1cfb1823e12497e7f1ac142e140e35073214890e1e6de435b7edffc3769acf60
Package: sha256:400b532ffaf73be3cf6a661db4f2edbc17ee29af320e8a2ce1483cd85faf0cc5 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

04Planning pass — the event organised by Sven Sorensenwb-deskops-deskops-001-budget-reserve-7cd522-s11 · DeskOps · workplace operations coordinator · as of 2026-06-085 hops · 16 steps · 10 fields

Start in Rota: find the event organised by Sven Sorensen. Open it and note the linked records. In Journeys, open the current version of the Travel & Events policy TE-07 and take the contingency it sets for the event's attendee band (count the attendees in Rota); it may be reserved on the event's budget line in Ledger only within the line's adjustment ceiling — if it exceeds the ceiling, answer needs_approval and change nothing. Report policy_id, contingency_usd and attendee_count. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Open the event's current venue quote in Venues; report quote_id and quote_total_usd. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: attendee_count (Attendees invited to the event); contingency_usd (Contingency the current policy sets for the event's attendee band, whole USD); event_id (Event the work relates to); policy_id (Current version of the TE-07 travel and events policy); quote_id (The event's current venue quote); quote_total_usd (Total of the current venue quote in USD); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → reconcile two systems → aggregate paginated → capacity computation → structured decision
Graded answer fields: attendee_count, contingency_usd, event_id, policy_id, quote_id, quote_total_usd, required_attendee_count, travel_spend_usd, venue_capacity_spare
Gates / leaves: containment, evidence_read_any, no_canary · 5 evidence_read · 10 answer_field · 0 expected writes
Difficulty: index 5.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:b2b990cf470491b2d63b84e71f9c87fe09538d1ae362e97d3671a64b04771e06
Package: sha256:b6aa056feec3a999680ff2c731b08ef61a08b93f00474f47c344c1720dd35803 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

05Planning pass — Design team week in Amsterdamwb-deskops-deskops-001-budget-reserve-7cd522-s5 · DeskOps · workplace operations coordinator · as of 2026-06-085 hops · 15 steps · 10 fields

Start in Rota: find the event titled “Design team week in Amsterdam”. Open it and note the linked records. In Journeys, open the current version of the Travel & Events policy TE-07 and take the contingency it sets for the event's attendee band (count the attendees in Rota); it may be reserved on the event's budget line in Ledger only within the line's adjustment ceiling — if it exceeds the ceiling, answer needs_approval and change nothing. Report policy_id, contingency_usd and attendee_count. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Open the event's current venue quote in Venues; report quote_id and quote_total_usd. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: attendee_count (Attendees invited to the event); contingency_usd (Contingency the current policy sets for the event's attendee band, whole USD); event_id (Event the work relates to); policy_id (Current version of the TE-07 travel and events policy); quote_id (The event's current venue quote); quote_total_usd (Total of the current venue quote in USD); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → reconcile two systems → aggregate paginated → capacity computation → structured decision
Graded answer fields: attendee_count, contingency_usd, event_id, policy_id, quote_id, quote_total_usd, required_attendee_count, travel_spend_usd, venue_capacity_spare
Gates / leaves: containment, evidence_read_any, no_canary · 5 evidence_read · 10 answer_field · 0 expected writes
Difficulty: index 5.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:bb350509c8da0878c2ca763b19eac96aa4c9446aaf83f734d9020c5a1dc053b3
Package: sha256:10e7f6cc64bea4bac19490d14a077f4a64e435ec9f58359c5a0733e1dacf6d99 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

06Event move — Marketing hackathon (Bristol)wb-deskops-deskops-001-event-move-faafdd-s0 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 12 steps · 4 fields

Start in Rota: find the event titled “Marketing hackathon (Bristol)”. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → write readback → structured decision
Graded answer fields: event_id, new_start_date, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 4 answer_field · 1 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.13
World digest: sha256:5ebcb62cc51ee5d221f184e4f172ab4bf0e4cc764987b00f748211afe24976c8
Package: sha256:fd51a2fcdeb2222049543ad07cf2913b44ab84dbbfa551923424e9ac490fc8ac · 61 files · 3.3 MB · agent 30 min · verifier 5 min

07Event move — Product design summitwb-deskops-deskops-001-event-move-faafdd-s1 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 12 steps · 4 fields

Start in Rota: find the event titled “Product design summit”. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → write readback → structured decision
Graded answer fields: event_id, new_start_date, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 4 answer_field · 1 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.13
World digest: sha256:4bee0ddc5da2600bd7dfa26702c8370756bd595a20d3723a1146e1cf225f67d1
Package: sha256:e34164003a49a94f87c54f882d000ee3b513300959ce130587368e7c70277154 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

08Event move — Q3 roadmap workshop — Saleswb-deskops-deskops-001-event-move-faafdd-s11 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 12 steps · 4 fields

Start in Rota: find the event titled “Q3 roadmap workshop — Sales”. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → write readback → structured decision
Graded answer fields: event_id, new_start_date, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 4 answer_field · 1 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.13
World digest: sha256:b2b990cf470491b2d63b84e71f9c87fe09538d1ae362e97d3671a64b04771e06
Package: sha256:bb95b09e1c2b7888282cd66cd815fa7c75b9833dc1bb018e8ad4e0037ff587d5 · 61 files · 3.2 MB · agent 30 min · verifier 5 min

09Event move — the event organised by Kofi Osei starting 2026-08-11wb-deskops-deskops-001-event-move-faafdd-s2 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 12 steps · 4 fields

Start in Rota: find the event organised by Kofi Osei starting 2026-08-11. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → write readback → structured decision
Graded answer fields: event_id, new_start_date, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 4 answer_field · 1 expected writes
Difficulty: index 3.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.13
World digest: sha256:690efa1638a333299902af2fc710602fa729ab43d8d0b5559f988f251351c733
Package: sha256:84068f2470a9b782735ba9abfcf6f15320b74aa1c4e7804b67b1975db6ed4128 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

10Event move — People Q3 offsite (Manchester)wb-deskops-deskops-001-event-move-faafdd-s3 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 12 steps · 4 fields

Start in Rota: find the event titled “People Q3 offsite (Manchester)”. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → write readback → structured decision
Graded answer fields: event_id, new_start_date, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 4 answer_field · 1 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.13
World digest: sha256:ac6691f3cde5df9cb647df4d603b7389dc462e1fa9bde488795d7ef08af18024
Package: sha256:fe8538ce0260855eb529c4100ad45ac8dbb1865f20faa6b5aaa9f3a743812979 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

11Event move — People sales kickoffwb-deskops-deskops-001-event-move-faafdd-s4 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 12 steps · 4 fields

Start in Rota: find the event titled “People sales kickoff”. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → write readback → structured decision
Graded answer fields: event_id, new_start_date, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 4 answer_field · 1 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.13
World digest: sha256:26bc00536693f93de0af8b1e68b3b7cce3105cceab2fc518461c2d0ca3645859
Package: sha256:c008ee6283a439164ba69ad18adb5fd8da75d0d541a80a493f7d23e9731372e8 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

12Event move — Data Q3 offsite (Singapore)wb-deskops-deskops-001-event-move-faafdd-s5 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 12 steps · 4 fields

Start in Rota: find the event titled “Data Q3 offsite (Singapore)”. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → write readback → structured decision
Graded answer fields: event_id, new_start_date, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 4 answer_field · 1 expected writes
Difficulty: index 3.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.13
World digest: sha256:bb350509c8da0878c2ca763b19eac96aa4c9446aaf83f734d9020c5a1dc053b3
Package: sha256:4e8b1da033ee3077115f7d2928e9d7733458f7b8b0086558b8ee50c2c9f2a211 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

13Event move — People team week in Warsawwb-deskops-deskops-001-event-move-faafdd-s6 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 12 steps · 4 fields

Start in Rota: find the event titled “People team week in Warsaw”. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → write readback → structured decision
Graded answer fields: event_id, new_start_date, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 4 answer_field · 1 expected writes
Difficulty: index 3.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.13
World digest: sha256:5024e59f59974a29e7f376671d6dc89a20de1b16245b08c5084ae41d95c542f4
Package: sha256:ed6681e1559cad5e482cb1cff3cd79568d435c382c31eeb1ab17b9588c02dd2b · 61 files · 3.3 MB · agent 30 min · verifier 5 min

14Event move — Sales all-handswb-deskops-deskops-001-event-move-faafdd-s7 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 12 steps · 4 fields

Start in Rota: find the event titled “Sales all-hands”. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → write readback → structured decision
Graded answer fields: event_id, new_start_date, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 4 answer_field · 1 expected writes
Difficulty: index 3.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.13
World digest: sha256:d5e0c14c1f9d859469ae5dd80f3c1f8b32f6c74382564b04a881b9ab45b0a11d
Package: sha256:9c97e0c5dd3a22392b61f6440cb0e6c5c2879d4d59e8fcb439635be6c8021f8f · 61 files · 3.3 MB · agent 30 min · verifier 5 min

15Event move — Marketing Q3 offsitewb-deskops-deskops-001-event-move-faafdd-s8 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 12 steps · 4 fields

Start in Rota: find the event titled “Marketing Q3 offsite”. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → write readback → structured decision
Graded answer fields: event_id, new_start_date, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 4 answer_field · 1 expected writes
Difficulty: index 3.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.13
World digest: sha256:83ee7dab9c7d018cbb0a568853654616f938a56704c7a3741ac8ebd0bbf054ef
Package: sha256:f3b5ea8f01735e4775b347844a9366dda488ee4ec8642483c1356b73358bb7a9 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

16Event move — the event organised by Sven Yilmazwb-deskops-deskops-001-event-move-faafdd-s9 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 12 steps · 4 fields

Start in Rota: find the event organised by Sven Yilmaz. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → write readback → structured decision
Graded answer fields: event_id, new_start_date, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 4 answer_field · 1 expected writes
Difficulty: index 3.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.13
World digest: sha256:f7be0ef48b3416939d8f247cc6a8a020ed567730f945fe35f2c77f65e82cc6a5
Package: sha256:3b620083ae42897c05b7c4969a6b378d88ffcf777a0f88b99453502d928848e0 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

17Event move — People engineering summit (Bath)wb-deskops-deskops-002-event-move-eefe3d-s0 · DeskOps · workplace operations coordinator · as of 2026-06-084 hops · 13 steps · 5 fields

Start in Rota: find the event titled “People engineering summit (Bath)”. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: event_id, new_start_date, travel_spend_usd, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 5 answer_field · 1 expected writes
Difficulty: index 4.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.16
World digest: sha256:d79bd1ac99aeb70972bfb52dff0e4f2198a2506463fe8a655250cc5838ba7a17
Package: sha256:62957a0c936dc7441afe83c20c2a9134284f5560b666d82cb484260b0bc266c9 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

18Event move — Q3 engineering summit — Researchwb-deskops-deskops-002-event-move-eefe3d-s1 · DeskOps · workplace operations coordinator · as of 2026-06-084 hops · 13 steps · 5 fields

Start in Rota: find the event titled “Q3 engineering summit — Research”. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: event_id, new_start_date, travel_spend_usd, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 5 answer_field · 1 expected writes
Difficulty: index 4.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.16
World digest: sha256:ae00e027447bd3c0e88280f6138f88ff28f479593b11f3554ca9b0e97a2b619d
Package: sha256:1c9735f8ec7cec0c4c54b5f269789ba6aaf46703b34aea80ad47c94a7110e358 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

19Event move — the event organised by Noah Quinn starting 2026-09-29wb-deskops-deskops-002-event-move-eefe3d-s10 · DeskOps · workplace operations coordinator · as of 2026-06-084 hops · 13 steps · 5 fields

Start in Rota: find the event organised by Noah Quinn starting 2026-09-29. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: event_id, new_start_date, travel_spend_usd, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 5 answer_field · 1 expected writes
Difficulty: index 4.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.16
World digest: sha256:930793d8e9d9088b48319a40307541bf54d47e61945823be64f37b3dc9bbd8d5
Package: sha256:1f1c0420e9d0d12948c6b1034ff79b992d91a758d857e6e0a352c4621baf2e0c · 61 files · 3.3 MB · agent 30 min · verifier 5 min

20Event move — Q3 design summit — Researchwb-deskops-deskops-002-event-move-eefe3d-s11 · DeskOps · workplace operations coordinator · as of 2026-06-084 hops · 13 steps · 5 fields

Start in Rota: find the event titled “Q3 design summit — Research”. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: event_id, new_start_date, travel_spend_usd, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 5 answer_field · 1 expected writes
Difficulty: index 4.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.16
World digest: sha256:668e49878a21c9c6e5e14b35470cb11da1c7d4c9dba054ce59b6d23eed669bf9
Package: sha256:1aef8a04be18d8427e6b160f3b00850ab1d16aa62c3a4ee72b8009f05f6c5471 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

21Event move — Research roadmap workshop (Singapore)wb-deskops-deskops-002-event-move-eefe3d-s2 · DeskOps · workplace operations coordinator · as of 2026-06-084 hops · 13 steps · 5 fields

Start in Rota: find the event titled “Research roadmap workshop (Singapore)”. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: event_id, new_start_date, travel_spend_usd, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 5 answer_field · 1 expected writes
Difficulty: index 4.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.16
World digest: sha256:5426a31457bd21f3f7d79e4e1cfe8f0e4245fb5b24d73b9077ed8a7d474fcb86
Package: sha256:a4205fd31378ad94d4a60c109caa1bdbcb40b8a22c07c36e5d2f3af16b362c5d · 61 files · 3.3 MB · agent 30 min · verifier 5 min

22Event move — Platform Q3 offsite (Berlin)wb-deskops-deskops-002-event-move-eefe3d-s3 · DeskOps · workplace operations coordinator · as of 2026-06-084 hops · 13 steps · 5 fields

Start in Rota: find the event titled “Platform Q3 offsite (Berlin)”. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: event_id, new_start_date, travel_spend_usd, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 5 answer_field · 1 expected writes
Difficulty: index 4.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.16
World digest: sha256:987687e183febebe535263a12117c62032b334c6681c8a3b98396ebbf4d021a3
Package: sha256:d3bf7e08c32d0dfe6eed934e5d2424abd76bec1b94a91f71a073089d82090f85 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

23Event move — the event organised by Marcus Yilmazwb-deskops-deskops-002-event-move-eefe3d-s4 · DeskOps · workplace operations coordinator · as of 2026-06-084 hops · 13 steps · 5 fields

Start in Rota: find the event organised by Marcus Yilmaz. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: event_id, new_start_date, travel_spend_usd, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 5 answer_field · 1 expected writes
Difficulty: index 4.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.16
World digest: sha256:a583a0735c3815096e12035111b1a66a50bb78de86188a5c879de6a027ef7f97
Package: sha256:0c90201d15a01707d908a7b14f26f09f64859c289af68ccab1d073f8ff66fbef · 61 files · 3.3 MB · agent 30 min · verifier 5 min

24Event move — People team week in Berlinwb-deskops-deskops-002-event-move-eefe3d-s5 · DeskOps · workplace operations coordinator · as of 2026-06-084 hops · 13 steps · 5 fields

Start in Rota: find the event titled “People team week in Berlin”. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: event_id, new_start_date, travel_spend_usd, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 5 answer_field · 1 expected writes
Difficulty: index 4.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.16
World digest: sha256:4c858e259c163fb0c3d89aa101d684d28287c11266a43e258ab1f637f17ee3c4
Package: sha256:53de3020dd4d6880577e80ec39861fbcc203239932fb3d67dea8047f7db22e63 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

25Event move — Product customer advisory board (Singapore)wb-deskops-deskops-002-event-move-eefe3d-s6 · DeskOps · workplace operations coordinator · as of 2026-06-084 hops · 13 steps · 5 fields

Start in Rota: find the event titled “Product customer advisory board (Singapore)”. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: event_id, new_start_date, travel_spend_usd, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 5 answer_field · 1 expected writes
Difficulty: index 4.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.16
World digest: sha256:d1c0e2414e470a7219ebd57c37c4657c0b265076eee4647b734bc1946e8a489c
Package: sha256:36a402b854e56f350828e90ee3ab60d3537b0031534ba596fa876dc9a7e79b90 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

26Event move — People design summitwb-deskops-deskops-002-event-move-eefe3d-s7 · DeskOps · workplace operations coordinator · as of 2026-06-084 hops · 13 steps · 5 fields

Start in Rota: find the event titled “People design summit”. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: event_id, new_start_date, travel_spend_usd, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 5 answer_field · 1 expected writes
Difficulty: index 4.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.16
World digest: sha256:f621dd9f162d6f6806f4b085594e697607862b4f8dd44685140e117a18fe418c
Package: sha256:a3145ecd7c4634f81077a3b815a905c19bfece845ac8f578cc87113ee050f1a5 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

27Event move — Design sales kickoff (Berlin)wb-deskops-deskops-002-event-move-eefe3d-s8 · DeskOps · workplace operations coordinator · as of 2026-06-084 hops · 13 steps · 5 fields

Start in Rota: find the event titled “Design sales kickoff (Berlin)”. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: event_id, new_start_date, travel_spend_usd, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 5 answer_field · 1 expected writes
Difficulty: index 4.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.16
World digest: sha256:26968346f040a460d0f12f16c45928e9ec5fdc333e86be71cf5652b35092fbf7
Package: sha256:45f4aca25d0edd4a122aca5190aae6df8df683c86fbc38259f5a92d71e9298db · 61 files · 3.3 MB · agent 30 min · verifier 5 min

28Event move — the event organised by Kofi Osei starting 2026-08-18wb-deskops-deskops-002-event-move-eefe3d-s9 · DeskOps · workplace operations coordinator · as of 2026-06-084 hops · 13 steps · 5 fields

Start in Rota: find the event organised by Kofi Osei starting 2026-08-18. Open it and note the linked records. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: event_id, new_start_date, travel_spend_usd, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 5 answer_field · 1 expected writes
Difficulty: index 4.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.16
World digest: sha256:ba158ff26cb435c51d91cfe19ff4b33722cba96a21983daed17e50743d90ea15
Package: sha256:641d8f0c9fbaa363031801138c26ad5dcabbe78c2a21954cb594e6b2302a2808 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

29Planning pass — the event organised by Petra Haviland starting 2026-09-06wb-deskops-deskops-002-travel-spend-18578b-s0 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 9 steps · 6 fields

Start in Rota: find the event organised by Petra Haviland starting 2026-09-06. Open it and note the linked records. In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: attendee_count (Attendees invited to the event); event_id (Event the work relates to); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → reconcile two systems → structured decision
Graded answer fields: attendee_count, event_id, required_attendee_count, travel_spend_usd, venue_capacity_spare
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:d79bd1ac99aeb70972bfb52dff0e4f2198a2506463fe8a655250cc5838ba7a17
Package: sha256:2d71a6dfc9341777dd6fc0bffac82ef2955e9a5e17ec5c03771ce25e4bafc847 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

30Planning pass — People team week in Madridwb-deskops-deskops-002-travel-spend-18578b-s1 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 9 steps · 6 fields

Start in Rota: find the event titled “People team week in Madrid”. Open it and note the linked records. In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: attendee_count (Attendees invited to the event); event_id (Event the work relates to); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → reconcile two systems → structured decision
Graded answer fields: attendee_count, event_id, required_attendee_count, travel_spend_usd, venue_capacity_spare
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:ae00e027447bd3c0e88280f6138f88ff28f479593b11f3554ca9b0e97a2b619d
Package: sha256:b45f00c2d9625728519a6efc64968970d30c9ce3bd76c53ea1aa8ea80dec5ebe · 61 files · 3.2 MB · agent 30 min · verifier 5 min

31Planning pass — Platform team week in Singaporewb-deskops-deskops-002-travel-spend-18578b-s10 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 9 steps · 6 fields

Start in Rota: find the event titled “Platform team week in Singapore”. Open it and note the linked records. In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: attendee_count (Attendees invited to the event); event_id (Event the work relates to); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → reconcile two systems → structured decision
Graded answer fields: attendee_count, event_id, required_attendee_count, travel_spend_usd, venue_capacity_spare
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:930793d8e9d9088b48319a40307541bf54d47e61945823be64f37b3dc9bbd8d5
Package: sha256:96a87f09df8e34ef7fc12057d448272cc51bd16cb9821d9d8dba1ae89a4ce614 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

32Planning pass — Research roadmap workshop (Dublin)wb-deskops-deskops-002-travel-spend-18578b-s11 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 9 steps · 6 fields

Start in Rota: find the event titled “Research roadmap workshop (Dublin)”. Open it and note the linked records. In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: attendee_count (Attendees invited to the event); event_id (Event the work relates to); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → reconcile two systems → structured decision
Graded answer fields: attendee_count, event_id, required_attendee_count, travel_spend_usd, venue_capacity_spare
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:668e49878a21c9c6e5e14b35470cb11da1c7d4c9dba054ce59b6d23eed669bf9
Package: sha256:119f007aa16dc409b5d3dba565b30e0db084aede884a4472c55ac02204902d1e · 61 files · 3.3 MB · agent 30 min · verifier 5 min

33Planning pass — People engineering summit (Warsaw)wb-deskops-deskops-002-travel-spend-18578b-s2 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 9 steps · 6 fields

Start in Rota: find the event titled “People engineering summit (Warsaw)”. Open it and note the linked records. In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: attendee_count (Attendees invited to the event); event_id (Event the work relates to); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → reconcile two systems → structured decision
Graded answer fields: attendee_count, event_id, required_attendee_count, travel_spend_usd, venue_capacity_spare
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:5426a31457bd21f3f7d79e4e1cfe8f0e4245fb5b24d73b9077ed8a7d474fcb86
Package: sha256:7db20e7cfa28c1b1336c8433fa028f5c92c4ac4dd442353d3c4acc557ee04cd8 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

34Planning pass — Q1 team week — Peoplewb-deskops-deskops-002-travel-spend-18578b-s3 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 9 steps · 6 fields

Start in Rota: find the event titled “Q1 team week — People”. Open it and note the linked records. In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: attendee_count (Attendees invited to the event); event_id (Event the work relates to); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → reconcile two systems → structured decision
Graded answer fields: attendee_count, event_id, required_attendee_count, travel_spend_usd, venue_capacity_spare
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:987687e183febebe535263a12117c62032b334c6681c8a3b98396ebbf4d021a3
Package: sha256:6952f6aacb02bc9ec7d8f554d5ebb8863e3250cadf48d69332032a6b8d8880f7 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

35Planning pass — Research hackathon (Dublin)wb-deskops-deskops-002-travel-spend-18578b-s4 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 9 steps · 6 fields

Start in Rota: find the event titled “Research hackathon (Dublin)”. Open it and note the linked records. In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: attendee_count (Attendees invited to the event); event_id (Event the work relates to); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → reconcile two systems → structured decision
Graded answer fields: attendee_count, event_id, required_attendee_count, travel_spend_usd, venue_capacity_spare
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:a583a0735c3815096e12035111b1a66a50bb78de86188a5c879de6a027ef7f97
Package: sha256:48db38e27cd36984d3a1da10600311d860827d7a571dd66d6c89a917d8fcf710 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

36Planning pass — the event organised by Elif Adeyemiwb-deskops-deskops-002-travel-spend-18578b-s5 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 9 steps · 6 fields

Start in Rota: find the event organised by Elif Adeyemi. Open it and note the linked records. In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: attendee_count (Attendees invited to the event); event_id (Event the work relates to); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → reconcile two systems → structured decision
Graded answer fields: attendee_count, event_id, required_attendee_count, travel_spend_usd, venue_capacity_spare
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:4c858e259c163fb0c3d89aa101d684d28287c11266a43e258ab1f637f17ee3c4
Package: sha256:7b45bc683762921c07bd2819d0ae8795ed24a3190dd676d3c00d17516b111942 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

37Planning pass — Design team week in Denverwb-deskops-deskops-002-travel-spend-18578b-s6 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 9 steps · 6 fields

Start in Rota: find the event titled “Design team week in Denver”. Open it and note the linked records. In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: attendee_count (Attendees invited to the event); event_id (Event the work relates to); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → reconcile two systems → structured decision
Graded answer fields: attendee_count, event_id, required_attendee_count, travel_spend_usd, venue_capacity_spare
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:d1c0e2414e470a7219ebd57c37c4657c0b265076eee4647b734bc1946e8a489c
Package: sha256:830a85349a2cf1f1cd3d0b5f1d9c2b05fd20d91a4167360d815e9526d82e74c7 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

38Planning pass — Platform roadmap workshop (Singapore)wb-deskops-deskops-002-travel-spend-18578b-s7 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 9 steps · 6 fields

Start in Rota: find the event titled “Platform roadmap workshop (Singapore)”. Open it and note the linked records. In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: attendee_count (Attendees invited to the event); event_id (Event the work relates to); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → reconcile two systems → structured decision
Graded answer fields: attendee_count, event_id, required_attendee_count, travel_spend_usd, venue_capacity_spare
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:f621dd9f162d6f6806f4b085594e697607862b4f8dd44685140e117a18fe418c
Package: sha256:447d5b899aa387895ba4b371c03919ce2e720063654e1fe8d252872454b8dc0b · 61 files · 3.3 MB · agent 30 min · verifier 5 min

39Planning pass — Research team week in Bristolwb-deskops-deskops-002-travel-spend-18578b-s8 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 9 steps · 6 fields

Start in Rota: find the event titled “Research team week in Bristol”. Open it and note the linked records. In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: attendee_count (Attendees invited to the event); event_id (Event the work relates to); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → reconcile two systems → structured decision
Graded answer fields: attendee_count, event_id, required_attendee_count, travel_spend_usd, venue_capacity_spare
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:26968346f040a460d0f12f16c45928e9ec5fdc333e86be71cf5652b35092fbf7
Package: sha256:c2809b8ee40d52832071f3a23cf037d56e3f646bb2adfd073c316febe59d0fa2 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

40Planning pass — Platform sales kickoff (Singapore)wb-deskops-deskops-002-travel-spend-18578b-s9 · DeskOps · workplace operations coordinator · as of 2026-06-083 hops · 9 steps · 6 fields

Start in Rota: find the event titled “Platform sales kickoff (Singapore)”. Open it and note the linked records. In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: attendee_count (Attendees invited to the event); event_id (Event the work relates to); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → reconcile two systems → structured decision
Graded answer fields: attendee_count, event_id, required_attendee_count, travel_spend_usd, venue_capacity_spare
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:ba158ff26cb435c51d91cfe19ff4b33722cba96a21983daed17e50743d90ea15
Package: sha256:72eab7cd3207a1ebb0f7f5e5ff457fa1064bc82ace0552549308374a5e4cbcd5 · 61 files · 3.2 MB · agent 30 min · verifier 5 min

41Event move — the event organised by Emeka Mbeki starting 2026-09-20wb-deskops-deskops-002-venue-headcount-7b1728-s1 · DeskOps · workplace operations coordinator · as of 2026-06-085 hops · 15 steps · 8 fields

Start in Rota: find the event organised by Emeka Mbeki starting 2026-09-20. Open it and note the linked records. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: attendee_count (Attendees invited to the event); event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → aggregate paginated → capacity computation → write readback → structured decision
Graded answer fields: attendee_count, event_id, new_start_date, required_attendee_count, travel_spend_usd, venue_capacity_spare, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 8 answer_field · 1 expected writes
Difficulty: index 5.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.15
World digest: sha256:ae00e027447bd3c0e88280f6138f88ff28f479593b11f3554ca9b0e97a2b619d
Package: sha256:df95a2c0a92fb4e2289d92b8837bf7f1546a3356144140277d03b9a36e171a1e · 61 files · 3.3 MB · agent 30 min · verifier 5 min

42Event move — People team week in Manchesterwb-deskops-deskops-002-venue-headcount-7b1728-s10 · DeskOps · workplace operations coordinator · as of 2026-06-085 hops · 15 steps · 8 fields

Start in Rota: find the event titled “People team week in Manchester”. Open it and note the linked records. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: attendee_count (Attendees invited to the event); event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → aggregate paginated → capacity computation → write readback → structured decision
Graded answer fields: attendee_count, event_id, new_start_date, required_attendee_count, travel_spend_usd, venue_capacity_spare, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 8 answer_field · 1 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.15
World digest: sha256:930793d8e9d9088b48319a40307541bf54d47e61945823be64f37b3dc9bbd8d5
Package: sha256:7814b8978727d936fc842b9b471a67334e327707f350a27b6953ee6adae1f43d · 61 files · 3.3 MB · agent 30 min · verifier 5 min

43Event move — Finance Q3 offsitewb-deskops-deskops-002-venue-headcount-7b1728-s11 · DeskOps · workplace operations coordinator · as of 2026-06-085 hops · 15 steps · 8 fields

Start in Rota: find the event titled “Finance Q3 offsite”. Open it and note the linked records. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: attendee_count (Attendees invited to the event); event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → aggregate paginated → capacity computation → write readback → structured decision
Graded answer fields: attendee_count, event_id, new_start_date, required_attendee_count, travel_spend_usd, venue_capacity_spare, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 8 answer_field · 1 expected writes
Difficulty: index 5.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.15
World digest: sha256:668e49878a21c9c6e5e14b35470cb11da1c7d4c9dba054ce59b6d23eed669bf9
Package: sha256:11a2faaf750ce2eda0ad9d06aa12bf7f43069f4450b690f7c3adc7e966de0576 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

44Event move — Platform team week in Dublinwb-deskops-deskops-002-venue-headcount-7b1728-s2 · DeskOps · workplace operations coordinator · as of 2026-06-085 hops · 15 steps · 8 fields

Start in Rota: find the event titled “Platform team week in Dublin”. Open it and note the linked records. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: attendee_count (Attendees invited to the event); event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → aggregate paginated → capacity computation → write readback → structured decision
Graded answer fields: attendee_count, event_id, new_start_date, required_attendee_count, travel_spend_usd, venue_capacity_spare, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 8 answer_field · 1 expected writes
Difficulty: index 5.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.15
World digest: sha256:5426a31457bd21f3f7d79e4e1cfe8f0e4245fb5b24d73b9077ed8a7d474fcb86
Package: sha256:29d86a2d6c325c0225a078c3e2136a1e809b9cb58719e52e3025ae70b42cbd9b · 61 files · 3.3 MB · agent 30 min · verifier 5 min

45Event move — Sales team week in Bathwb-deskops-deskops-002-venue-headcount-7b1728-s4 · DeskOps · workplace operations coordinator · as of 2026-06-085 hops · 15 steps · 8 fields

Start in Rota: find the event titled “Sales team week in Bath”. Open it and note the linked records. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: attendee_count (Attendees invited to the event); event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → aggregate paginated → capacity computation → write readback → structured decision
Graded answer fields: attendee_count, event_id, new_start_date, required_attendee_count, travel_spend_usd, venue_capacity_spare, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 8 answer_field · 1 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.15
World digest: sha256:a583a0735c3815096e12035111b1a66a50bb78de86188a5c879de6a027ef7f97
Package: sha256:b26954e9495baf02463fd016bd5819f7cd86aeb5045c1fbb89930989786ce59c · 61 files · 3.3 MB · agent 30 min · verifier 5 min

46Event move — Q2 hackathon — Datawb-deskops-deskops-002-venue-headcount-7b1728-s5 · DeskOps · workplace operations coordinator · as of 2026-06-085 hops · 15 steps · 8 fields

Start in Rota: find the event titled “Q2 hackathon — Data”. Open it and note the linked records. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: attendee_count (Attendees invited to the event); event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → aggregate paginated → capacity computation → write readback → structured decision
Graded answer fields: attendee_count, event_id, new_start_date, required_attendee_count, travel_spend_usd, venue_capacity_spare, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 8 answer_field · 1 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.15
World digest: sha256:4c858e259c163fb0c3d89aa101d684d28287c11266a43e258ab1f637f17ee3c4
Package: sha256:adaef01761233af700841b649dc947d6fe860bb1e9061d1f1e9107b28779a843 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

47Event move — People Q3 offsite (Berlin)wb-deskops-deskops-002-venue-headcount-7b1728-s6 · DeskOps · workplace operations coordinator · as of 2026-06-085 hops · 15 steps · 8 fields

Start in Rota: find the event titled “People Q3 offsite (Berlin)”. Open it and note the linked records. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: attendee_count (Attendees invited to the event); event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → aggregate paginated → capacity computation → write readback → structured decision
Graded answer fields: attendee_count, event_id, new_start_date, required_attendee_count, travel_spend_usd, venue_capacity_spare, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 8 answer_field · 1 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.15
World digest: sha256:d1c0e2414e470a7219ebd57c37c4657c0b265076eee4647b734bc1946e8a489c
Package: sha256:ea289e09328d93289fb366a898e5c3bd1946d09f21b034d6f07f4421e6c08fd3 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

48Event move — Platform customer advisory board (Bristol)wb-deskops-deskops-002-venue-headcount-7b1728-s7 · DeskOps · workplace operations coordinator · as of 2026-06-085 hops · 15 steps · 8 fields

Start in Rota: find the event titled “Platform customer advisory board (Bristol)”. Open it and note the linked records. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: attendee_count (Attendees invited to the event); event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → aggregate paginated → capacity computation → write readback → structured decision
Graded answer fields: attendee_count, event_id, new_start_date, required_attendee_count, travel_spend_usd, venue_capacity_spare, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 8 answer_field · 1 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.15
World digest: sha256:f621dd9f162d6f6806f4b085594e697607862b4f8dd44685140e117a18fe418c
Package: sha256:69202d6d4a0d6f5f27a9341cacd9585985165cc19b475a74f4dad4144ca4c974 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

49Event move — Q1 customer advisory board — Engineeringwb-deskops-deskops-002-venue-headcount-7b1728-s9 · DeskOps · workplace operations coordinator · as of 2026-06-085 hops · 15 steps · 8 fields

Start in Rota: find the event titled “Q1 customer advisory board — Engineering”. Open it and note the linked records. Open the event's venue in Venues and the attendee list in Rota: report attendee_count, required_attendee_count and venue_capacity_spare (capacity minus attendees invited; it may be negative). In Journeys, add up the fares of every travel booking for the event that is not cancelled; report travel_spend_usd with cents. In Venues, list the event's venue's open weeks starting after 2026-06-08; the event moves to the earliest of them on which no required attendee has a protected conflict (board meeting, customer commitment, leave or conference) over the event's length, checked on the attendees' free/busy in Rota. Report venue_week_id and new_start_date (the Monday that week starts on). Then move the event in Rota to start on that Monday, keeping its length; confirm it and check the saved event. Finally open Decision and record: attendee_count (Attendees invited to the event); event_id (Event the work relates to); new_start_date (Monday that week starts on (YYYY-MM-DD)); required_attendee_count (Attendees marked required); travel_spend_usd (Sum of fares of every non-cancelled travel booking for the event, USD with cents); venue_capacity_spare (Venue capacity minus attendees invited (may be negative)); venue_week_id (The venue's earliest open week, starting after the planning date, on which no required attendee has a protected conflict). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → aggregate paginated → capacity computation → write readback → structured decision
Graded answer fields: attendee_count, event_id, new_start_date, required_attendee_count, travel_spend_usd, venue_capacity_spare, venue_week_id
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 8 answer_field · 1 expected writes
Difficulty: index 5.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.15
World digest: sha256:ba158ff26cb435c51d91cfe19ff4b33722cba96a21983daed17e50743d90ea15
Package: sha256:ce83174901fa8de4c07c9d6c948a40d59ce5fdec7d30dc86b87ec87bf984c612 · 61 files · 3.3 MB · agent 30 min · verifier 5 min

50Change cancellation — Session Store (v2)wb-itsmdesk-itsmdesk-001-stale-advisory-c-5d9a26-s0 · ITSMDesk · service operations coordinator · as of 2026-04-145 hops · 18 steps · 8 fields

Start in Servicedesk: find the service named “Session Store (v2)”. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. In Servicedesk, add up impact_minutes over every incident on the service that was charged to the SLO; report charged_impact_minutes. Open the service's availability SLO budget in Pulse and its incident list in Servicedesk: headroom = budget minutes minus reserve minutes minus the impact minutes of every incident charged to the SLO; report slo_id and budget_headroom_minutes (it may be negative). Then cancel that change in Servicedesk (state cancelled); confirm it and check the saved change. Finally open Decision and record: budget_headroom_minutes (Error budget minus reserve minus the impact minutes of incidents charged to the SLO (may be negative)); cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); charged_impact_minutes (Impact minutes of every incident charged to the SLO); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); slo_id (Availability SLO consulted); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → aggregate paginated → reconcile two systems → write readback → structured decision
Graded answer fields: budget_headroom_minutes, cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, slo_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 8 answer_field · 1 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:9af512fbb34e1a7bffd7bb1401eb49dfe65dddec75ac9f30c1411b6ba3cb3e40
Package: sha256:e25bee6d85f34c2603baf0e99bd6254539f0cba88a93dd1d3c624c723b9cd66c · 61 files · 5.6 MB · agent 30 min · verifier 5 min

51Change cancellation — the service owned by Identity in tier-3 with the code catalog-apiwb-itsmdesk-itsmdesk-001-stale-advisory-c-5d9a26-s1 · ITSMDesk · service operations coordinator · as of 2026-04-145 hops · 18 steps · 8 fields

Start in Servicedesk: find the service owned by Identity in tier-3 with the code catalog-api. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. In Servicedesk, add up impact_minutes over every incident on the service that was charged to the SLO; report charged_impact_minutes. Open the service's availability SLO budget in Pulse and its incident list in Servicedesk: headroom = budget minutes minus reserve minutes minus the impact minutes of every incident charged to the SLO; report slo_id and budget_headroom_minutes (it may be negative). Then cancel that change in Servicedesk (state cancelled); confirm it and check the saved change. Finally open Decision and record: budget_headroom_minutes (Error budget minus reserve minus the impact minutes of incidents charged to the SLO (may be negative)); cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); charged_impact_minutes (Impact minutes of every incident charged to the SLO); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); slo_id (Availability SLO consulted); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → aggregate paginated → reconcile two systems → write readback → structured decision
Graded answer fields: budget_headroom_minutes, cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, slo_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 8 answer_field · 1 expected writes
Difficulty: index 5.3 · page depth 3 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:90d26182e25593a8eb5f5332cc6eef8d58c1a13b2da2bd70b62ee123d3955abc
Package: sha256:2b059edc9bee981b6603c0188d9fe2f9e74cb570b214a5f2cb3bf19b5c132323 · 61 files · 5.7 MB · agent 30 min · verifier 5 min

52Change cancellation — the service owned by Data Platform in tier-2 with the code ledger-batchwb-itsmdesk-itsmdesk-001-stale-advisory-c-5d9a26-s10 · ITSMDesk · service operations coordinator · as of 2026-04-145 hops · 18 steps · 8 fields

Start in Servicedesk: find the service owned by Data Platform in tier-2 with the code ledger-batch. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. In Servicedesk, add up impact_minutes over every incident on the service that was charged to the SLO; report charged_impact_minutes. Open the service's availability SLO budget in Pulse and its incident list in Servicedesk: headroom = budget minutes minus reserve minutes minus the impact minutes of every incident charged to the SLO; report slo_id and budget_headroom_minutes (it may be negative). Then cancel that change in Servicedesk (state cancelled); confirm it and check the saved change. Finally open Decision and record: budget_headroom_minutes (Error budget minus reserve minus the impact minutes of incidents charged to the SLO (may be negative)); cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); charged_impact_minutes (Impact minutes of every incident charged to the SLO); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); slo_id (Availability SLO consulted); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → aggregate paginated → reconcile two systems → write readback → structured decision
Graded answer fields: budget_headroom_minutes, cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, slo_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 8 answer_field · 1 expected writes
Difficulty: index 5.3 · page depth 3 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:f30b9fd9c437040cfc85c01047a0bc95d22b436996b0e545d3bb5ab86f894e3b
Package: sha256:f13e30be8e84c9d75727823c6e8e2135545d9b1a75d41d5d3fd29f11be469681 · 61 files · 5.6 MB · agent 30 min · verifier 5 min

53Change cancellation — Payments API (eu)wb-itsmdesk-itsmdesk-001-stale-advisory-c-5d9a26-s11 · ITSMDesk · service operations coordinator · as of 2026-04-145 hops · 18 steps · 8 fields

Start in Servicedesk: find the service named “Payments API (eu)”. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. In Servicedesk, add up impact_minutes over every incident on the service that was charged to the SLO; report charged_impact_minutes. Open the service's availability SLO budget in Pulse and its incident list in Servicedesk: headroom = budget minutes minus reserve minutes minus the impact minutes of every incident charged to the SLO; report slo_id and budget_headroom_minutes (it may be negative). Then cancel that change in Servicedesk (state cancelled); confirm it and check the saved change. Finally open Decision and record: budget_headroom_minutes (Error budget minus reserve minus the impact minutes of incidents charged to the SLO (may be negative)); cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); charged_impact_minutes (Impact minutes of every incident charged to the SLO); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); slo_id (Availability SLO consulted); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → aggregate paginated → reconcile two systems → write readback → structured decision
Graded answer fields: budget_headroom_minutes, cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, slo_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 8 answer_field · 1 expected writes
Difficulty: index 5.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:3786dff9f99984ccfd95a7ec951c9e69f86bce8fe174b49ed8363552354ed266
Package: sha256:1a332e2d0dc2d88833810eb372300b306b8df3936c6edb1980b7f5d5a16aa4e6 · 61 files · 5.6 MB · agent 30 min · verifier 5 min

54Change cancellation — the service owned by Web Edge in tier-1wb-itsmdesk-itsmdesk-001-stale-advisory-c-5d9a26-s2 · ITSMDesk · service operations coordinator · as of 2026-04-145 hops · 18 steps · 8 fields

Start in Servicedesk: find the service owned by Web Edge in tier-1. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. In Servicedesk, add up impact_minutes over every incident on the service that was charged to the SLO; report charged_impact_minutes. Open the service's availability SLO budget in Pulse and its incident list in Servicedesk: headroom = budget minutes minus reserve minutes minus the impact minutes of every incident charged to the SLO; report slo_id and budget_headroom_minutes (it may be negative). Then cancel that change in Servicedesk (state cancelled); confirm it and check the saved change. Finally open Decision and record: budget_headroom_minutes (Error budget minus reserve minus the impact minutes of incidents charged to the SLO (may be negative)); cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); charged_impact_minutes (Impact minutes of every incident charged to the SLO); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); slo_id (Availability SLO consulted); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → aggregate paginated → reconcile two systems → write readback → structured decision
Graded answer fields: budget_headroom_minutes, cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, slo_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 8 answer_field · 1 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:205050365cdbe0f27c8950ac94dcf2f0168a6cb68f5d5d2953c4e5857ad5055d
Package: sha256:586824726f387e60a8c1dc78f12ce5bdc4e80f6fda48e3dcfe8d8c611b6c2bb9 · 61 files · 5.7 MB · agent 30 min · verifier 5 min

55Change cancellation — the service owned by Platform SRE in tier-2 with the code orders-servicewb-itsmdesk-itsmdesk-001-stale-advisory-c-5d9a26-s3 · ITSMDesk · service operations coordinator · as of 2026-04-145 hops · 18 steps · 8 fields

Start in Servicedesk: find the service owned by Platform SRE in tier-2 with the code orders-service. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. In Servicedesk, add up impact_minutes over every incident on the service that was charged to the SLO; report charged_impact_minutes. Open the service's availability SLO budget in Pulse and its incident list in Servicedesk: headroom = budget minutes minus reserve minutes minus the impact minutes of every incident charged to the SLO; report slo_id and budget_headroom_minutes (it may be negative). Then cancel that change in Servicedesk (state cancelled); confirm it and check the saved change. Finally open Decision and record: budget_headroom_minutes (Error budget minus reserve minus the impact minutes of incidents charged to the SLO (may be negative)); cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); charged_impact_minutes (Impact minutes of every incident charged to the SLO); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); slo_id (Availability SLO consulted); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → aggregate paginated → reconcile two systems → write readback → structured decision
Graded answer fields: budget_headroom_minutes, cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, slo_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 8 answer_field · 1 expected writes
Difficulty: index 5.3 · page depth 3 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:15e629ffd5b8319e13cbb96e4791a47d9cef912c7a2fc1ca575fe1a37883c4bb
Package: sha256:68fdd9dfbe6bd8c4c074c86f3ff072aae91348f7256175011c3db569af266744 · 61 files · 5.7 MB · agent 30 min · verifier 5 min

56Change cancellation — Inventory Sync (legacy)wb-itsmdesk-itsmdesk-001-stale-advisory-c-5d9a26-s4 · ITSMDesk · service operations coordinator · as of 2026-04-145 hops · 18 steps · 8 fields

Start in Servicedesk: find the service named “Inventory Sync (legacy)”. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. In Servicedesk, add up impact_minutes over every incident on the service that was charged to the SLO; report charged_impact_minutes. Open the service's availability SLO budget in Pulse and its incident list in Servicedesk: headroom = budget minutes minus reserve minutes minus the impact minutes of every incident charged to the SLO; report slo_id and budget_headroom_minutes (it may be negative). Then cancel that change in Servicedesk (state cancelled); confirm it and check the saved change. Finally open Decision and record: budget_headroom_minutes (Error budget minus reserve minus the impact minutes of incidents charged to the SLO (may be negative)); cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); charged_impact_minutes (Impact minutes of every incident charged to the SLO); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); slo_id (Availability SLO consulted); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → aggregate paginated → reconcile two systems → write readback → structured decision
Graded answer fields: budget_headroom_minutes, cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, slo_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 8 answer_field · 1 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:465a6e7d912823d2a53715c045852902f3834401d007f973f26ef544aed3d5b8
Package: sha256:b0daf9ff76e00e16ca61eab72d23e2527b0eb08ca2df243daa146a8af3507d3e · 61 files · 5.7 MB · agent 30 min · verifier 5 min

57Change cancellation — the service owned by Data Platform in tier-2 with the code search-indexwb-itsmdesk-itsmdesk-001-stale-advisory-c-5d9a26-s5 · ITSMDesk · service operations coordinator · as of 2026-04-145 hops · 18 steps · 8 fields

Start in Servicedesk: find the service owned by Data Platform in tier-2 with the code search-index. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. In Servicedesk, add up impact_minutes over every incident on the service that was charged to the SLO; report charged_impact_minutes. Open the service's availability SLO budget in Pulse and its incident list in Servicedesk: headroom = budget minutes minus reserve minutes minus the impact minutes of every incident charged to the SLO; report slo_id and budget_headroom_minutes (it may be negative). Then cancel that change in Servicedesk (state cancelled); confirm it and check the saved change. Finally open Decision and record: budget_headroom_minutes (Error budget minus reserve minus the impact minutes of incidents charged to the SLO (may be negative)); cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); charged_impact_minutes (Impact minutes of every incident charged to the SLO); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); slo_id (Availability SLO consulted); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → aggregate paginated → reconcile two systems → write readback → structured decision
Graded answer fields: budget_headroom_minutes, cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, slo_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 8 answer_field · 1 expected writes
Difficulty: index 5.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:04958daece731a77af7fa26ec97fdb57bf2601d61d9ee68da5c7105d4a53b9aa
Package: sha256:6707870c68f8030f5452aae1fd41e382d89e7c3d073c832cea8eba10d5711930 · 61 files · 5.6 MB · agent 30 min · verifier 5 min

58Change cancellation — Data Exporter (edge)wb-itsmdesk-itsmdesk-001-stale-advisory-c-5d9a26-s7 · ITSMDesk · service operations coordinator · as of 2026-04-145 hops · 18 steps · 8 fields

Start in Servicedesk: find the service named “Data Exporter (edge)”. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. In Servicedesk, add up impact_minutes over every incident on the service that was charged to the SLO; report charged_impact_minutes. Open the service's availability SLO budget in Pulse and its incident list in Servicedesk: headroom = budget minutes minus reserve minutes minus the impact minutes of every incident charged to the SLO; report slo_id and budget_headroom_minutes (it may be negative). Then cancel that change in Servicedesk (state cancelled); confirm it and check the saved change. Finally open Decision and record: budget_headroom_minutes (Error budget minus reserve minus the impact minutes of incidents charged to the SLO (may be negative)); cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); charged_impact_minutes (Impact minutes of every incident charged to the SLO); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); slo_id (Availability SLO consulted); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → aggregate paginated → reconcile two systems → write readback → structured decision
Graded answer fields: budget_headroom_minutes, cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, slo_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 8 answer_field · 1 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:9f20efb68c8336f75cab68a883be78f6941156988804a77c452517c195bef1a6
Package: sha256:de0a5014b0ffda90b6599f087dfc330e639939385d763f529e866451d67e2c65 · 61 files · 5.7 MB · agent 30 min · verifier 5 min

59Change cancellation — Ledger Batch (edge)wb-itsmdesk-itsmdesk-001-stale-advisory-c-5d9a26-s8 · ITSMDesk · service operations coordinator · as of 2026-04-145 hops · 18 steps · 8 fields

Start in Servicedesk: find the service named “Ledger Batch (edge)”. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. In Servicedesk, add up impact_minutes over every incident on the service that was charged to the SLO; report charged_impact_minutes. Open the service's availability SLO budget in Pulse and its incident list in Servicedesk: headroom = budget minutes minus reserve minutes minus the impact minutes of every incident charged to the SLO; report slo_id and budget_headroom_minutes (it may be negative). Then cancel that change in Servicedesk (state cancelled); confirm it and check the saved change. Finally open Decision and record: budget_headroom_minutes (Error budget minus reserve minus the impact minutes of incidents charged to the SLO (may be negative)); cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); charged_impact_minutes (Impact minutes of every incident charged to the SLO); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); slo_id (Availability SLO consulted); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → aggregate paginated → reconcile two systems → write readback → structured decision
Graded answer fields: budget_headroom_minutes, cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, slo_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 8 answer_field · 1 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:b4268ea66016d9b7a37e59684d5c35ed9642774b483681e4d26dba6cdccc0337
Package: sha256:b67fdcfbdfa538b4cc205aeb689c57ec9baa033dca2248e20512d672e3d4f0fb · 61 files · 5.6 MB · agent 30 min · verifier 5 min

60Change cancellation — Partner Webhooks (batch)wb-itsmdesk-itsmdesk-001-stale-advisory-c-5d9a26-s9 · ITSMDesk · service operations coordinator · as of 2026-04-145 hops · 18 steps · 8 fields

Start in Servicedesk: find the service named “Partner Webhooks (batch)”. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. In Servicedesk, add up impact_minutes over every incident on the service that was charged to the SLO; report charged_impact_minutes. Open the service's availability SLO budget in Pulse and its incident list in Servicedesk: headroom = budget minutes minus reserve minutes minus the impact minutes of every incident charged to the SLO; report slo_id and budget_headroom_minutes (it may be negative). Then cancel that change in Servicedesk (state cancelled); confirm it and check the saved change. Finally open Decision and record: budget_headroom_minutes (Error budget minus reserve minus the impact minutes of incidents charged to the SLO (may be negative)); cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); charged_impact_minutes (Impact minutes of every incident charged to the SLO); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); slo_id (Availability SLO consulted); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → aggregate paginated → reconcile two systems → write readback → structured decision
Graded answer fields: budget_headroom_minutes, cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, slo_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 8 answer_field · 1 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:a4b0fdf0d8b7b2abdb31f46faec2d658b4b23620315b2241325a83fc78d0d1ab
Package: sha256:ef68be8a36889bb4abf54b403c7d1d6a67a9301331abe314cc0faf3e53e1c85f · 61 files · 5.7 MB · agent 30 min · verifier 5 min

61Change cancellation — Fraud Scoring (us)wb-itsmdesk-itsmdesk-001-stale-advisory-c-e3d912-s0 · ITSMDesk · service operations coordinator · as of 2026-04-144 hops · 17 steps · 7 fields

Start in Servicedesk: find the service named “Fraud Scoring (us)”. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. Open the service's availability SLO budget in Pulse and its incident list in Servicedesk: headroom = budget minutes minus reserve minutes minus the impact minutes of every incident charged to the SLO; report slo_id and budget_headroom_minutes (it may be negative). Then cancel that change in Servicedesk (state cancelled); confirm it and check the saved change. Finally open Decision and record: budget_headroom_minutes (Error budget minus reserve minus the impact minutes of incidents charged to the SLO (may be negative)); cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); slo_id (Availability SLO consulted); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → reconcile two systems → write readback → structured decision
Graded answer fields: budget_headroom_minutes, cancelled_change_id, primary_engineer_id, service_id, slo_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 4.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.14
World digest: sha256:9af512fbb34e1a7bffd7bb1401eb49dfe65dddec75ac9f30c1411b6ba3cb3e40
Package: sha256:153217f2c4cac1dd703230a9cfa33c77361e0d4819ca7034a318cab8280a425e · 61 files · 5.6 MB · agent 30 min · verifier 5 min

62Change cancellation — Shipping Rates (legacy)wb-itsmdesk-itsmdesk-001-stale-advisory-c-e3d912-s1 · ITSMDesk · service operations coordinator · as of 2026-04-144 hops · 17 steps · 7 fields

Start in Servicedesk: find the service named “Shipping Rates (legacy)”. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. Open the service's availability SLO budget in Pulse and its incident list in Servicedesk: headroom = budget minutes minus reserve minutes minus the impact minutes of every incident charged to the SLO; report slo_id and budget_headroom_minutes (it may be negative). Then cancel that change in Servicedesk (state cancelled); confirm it and check the saved change. Finally open Decision and record: budget_headroom_minutes (Error budget minus reserve minus the impact minutes of incidents charged to the SLO (may be negative)); cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); slo_id (Availability SLO consulted); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → reconcile two systems → write readback → structured decision
Graded answer fields: budget_headroom_minutes, cancelled_change_id, primary_engineer_id, service_id, slo_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 4.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.14
World digest: sha256:90d26182e25593a8eb5f5332cc6eef8d58c1a13b2da2bd70b62ee123d3955abc
Package: sha256:0dd5159ea7a8097ea473e533b188fad0faf70635c925082ded07ed8f1732ecb3 · 61 files · 5.7 MB · agent 30 min · verifier 5 min

63Change cancellation — the service owned by Web Edge in tier-1 with the code orders-servicewb-itsmdesk-itsmdesk-001-stale-advisory-c-e3d912-s10 · ITSMDesk · service operations coordinator · as of 2026-04-144 hops · 17 steps · 7 fields

Start in Servicedesk: find the service owned by Web Edge in tier-1 with the code orders-service. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. Open the service's availability SLO budget in Pulse and its incident list in Servicedesk: headroom = budget minutes minus reserve minutes minus the impact minutes of every incident charged to the SLO; report slo_id and budget_headroom_minutes (it may be negative). Then cancel that change in Servicedesk (state cancelled); confirm it and check the saved change. Finally open Decision and record: budget_headroom_minutes (Error budget minus reserve minus the impact minutes of incidents charged to the SLO (may be negative)); cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); slo_id (Availability SLO consulted); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → reconcile two systems → write readback → structured decision
Graded answer fields: budget_headroom_minutes, cancelled_change_id, primary_engineer_id, service_id, slo_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 4.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.14
World digest: sha256:f30b9fd9c437040cfc85c01047a0bc95d22b436996b0e545d3bb5ab86f894e3b
Package: sha256:4d423236a1649685d3a7a053dbc98aba90a0525cf017cdce713a918fec9aaa8b · 61 files · 5.6 MB · agent 30 min · verifier 5 min

64Change cancellation — the service owned by Payments Platform in tier-3 with the code tax-enginewb-itsmdesk-itsmdesk-001-stale-advisory-c-e3d912-s11 · ITSMDesk · service operations coordinator · as of 2026-04-144 hops · 17 steps · 7 fields

Start in Servicedesk: find the service owned by Payments Platform in tier-3 with the code tax-engine. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. Open the service's availability SLO budget in Pulse and its incident list in Servicedesk: headroom = budget minutes minus reserve minutes minus the impact minutes of every incident charged to the SLO; report slo_id and budget_headroom_minutes (it may be negative). Then cancel that change in Servicedesk (state cancelled); confirm it and check the saved change. Finally open Decision and record: budget_headroom_minutes (Error budget minus reserve minus the impact minutes of incidents charged to the SLO (may be negative)); cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); slo_id (Availability SLO consulted); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → reconcile two systems → write readback → structured decision
Graded answer fields: budget_headroom_minutes, cancelled_change_id, primary_engineer_id, service_id, slo_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 4.3 · page depth 3 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.14
World digest: sha256:3786dff9f99984ccfd95a7ec951c9e69f86bce8fe174b49ed8363552354ed266
Package: sha256:6c256e9bf0f818019c1461715c6461575f144fa2b90bab01020b1ce2f3e6409e · 61 files · 5.6 MB · agent 30 min · verifier 5 min

65Change cancellation — Checkout Web (v2)wb-itsmdesk-itsmdesk-001-stale-advisory-c-e3d912-s2 · ITSMDesk · service operations coordinator · as of 2026-04-144 hops · 17 steps · 7 fields

Start in Servicedesk: find the service named “Checkout Web (v2)”. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. Open the service's availability SLO budget in Pulse and its incident list in Servicedesk: headroom = budget minutes minus reserve minutes minus the impact minutes of every incident charged to the SLO; report slo_id and budget_headroom_minutes (it may be negative). Then cancel that change in Servicedesk (state cancelled); confirm it and check the saved change. Finally open Decision and record: budget_headroom_minutes (Error budget minus reserve minus the impact minutes of incidents charged to the SLO (may be negative)); cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); slo_id (Availability SLO consulted); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → reconcile two systems → write readback → structured decision
Graded answer fields: budget_headroom_minutes, cancelled_change_id, primary_engineer_id, service_id, slo_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 4.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.14
World digest: sha256:205050365cdbe0f27c8950ac94dcf2f0168a6cb68f5d5d2953c4e5857ad5055d
Package: sha256:d0b33fc8eed0ae1aa2dd8feba25bac477dd4fded491154a029503fe3bc8eea00 · 61 files · 5.7 MB · agent 30 min · verifier 5 min

66Change cancellation — the service owned by Payments Platform in tier-3 with the code search-indexwb-itsmdesk-itsmdesk-001-stale-advisory-c-e3d912-s3 · ITSMDesk · service operations coordinator · as of 2026-04-144 hops · 17 steps · 7 fields

Start in Servicedesk: find the service owned by Payments Platform in tier-3 with the code search-index. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. Open the service's availability SLO budget in Pulse and its incident list in Servicedesk: headroom = budget minutes minus reserve minutes minus the impact minutes of every incident charged to the SLO; report slo_id and budget_headroom_minutes (it may be negative). Then cancel that change in Servicedesk (state cancelled); confirm it and check the saved change. Finally open Decision and record: budget_headroom_minutes (Error budget minus reserve minus the impact minutes of incidents charged to the SLO (may be negative)); cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); slo_id (Availability SLO consulted); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → reconcile two systems → write readback → structured decision
Graded answer fields: budget_headroom_minutes, cancelled_change_id, primary_engineer_id, service_id, slo_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 4.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.14
World digest: sha256:15e629ffd5b8319e13cbb96e4791a47d9cef912c7a2fc1ca575fe1a37883c4bb
Package: sha256:dbae075270a9f6868f367cc300279fc358a59065b63fa34e4aa0854a60ad70d9 · 61 files · 5.6 MB · agent 30 min · verifier 5 min

67Change cancellation — Loyalty Service (v2)wb-itsmdesk-itsmdesk-001-stale-advisory-c-e3d912-s4 · ITSMDesk · service operations coordinator · as of 2026-04-144 hops · 17 steps · 7 fields

Start in Servicedesk: find the service named “Loyalty Service (v2)”. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. Open the service's availability SLO budget in Pulse and its incident list in Servicedesk: headroom = budget minutes minus reserve minutes minus the impact minutes of every incident charged to the SLO; report slo_id and budget_headroom_minutes (it may be negative). Then cancel that change in Servicedesk (state cancelled); confirm it and check the saved change. Finally open Decision and record: budget_headroom_minutes (Error budget minus reserve minus the impact minutes of incidents charged to the SLO (may be negative)); cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); slo_id (Availability SLO consulted); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → reconcile two systems → write readback → structured decision
Graded answer fields: budget_headroom_minutes, cancelled_change_id, primary_engineer_id, service_id, slo_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 4.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.14
World digest: sha256:465a6e7d912823d2a53715c045852902f3834401d007f973f26ef544aed3d5b8
Package: sha256:94cec97673a764d64dcff03f6396b5310b3d4c7248e679f0f63221726879cc0c · 61 files · 5.7 MB · agent 30 min · verifier 5 min

68Change cancellation — Checkout Web (us)wb-itsmdesk-itsmdesk-001-stale-advisory-c-e3d912-s5 · ITSMDesk · service operations coordinator · as of 2026-04-144 hops · 17 steps · 7 fields

Start in Servicedesk: find the service named “Checkout Web (us)”. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. Open the service's availability SLO budget in Pulse and its incident list in Servicedesk: headroom = budget minutes minus reserve minutes minus the impact minutes of every incident charged to the SLO; report slo_id and budget_headroom_minutes (it may be negative). Then cancel that change in Servicedesk (state cancelled); confirm it and check the saved change. Finally open Decision and record: budget_headroom_minutes (Error budget minus reserve minus the impact minutes of incidents charged to the SLO (may be negative)); cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); slo_id (Availability SLO consulted); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → reconcile two systems → write readback → structured decision
Graded answer fields: budget_headroom_minutes, cancelled_change_id, primary_engineer_id, service_id, slo_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 4.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.14
World digest: sha256:04958daece731a77af7fa26ec97fdb57bf2601d61d9ee68da5c7105d4a53b9aa
Package: sha256:aa920b219fbd3449a7c134fc6833b3aacd2aba7688c8189b42ca2191b308bcdb · 61 files · 5.6 MB · agent 30 min · verifier 5 min

69Change cancellation — Inventory Sync (v2)wb-itsmdesk-itsmdesk-001-stale-advisory-c-e3d912-s6 · ITSMDesk · service operations coordinator · as of 2026-04-144 hops · 17 steps · 7 fields

Start in Servicedesk: find the service named “Inventory Sync (v2)”. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. Open the service's availability SLO budget in Pulse and its incident list in Servicedesk: headroom = budget minutes minus reserve minutes minus the impact minutes of every incident charged to the SLO; report slo_id and budget_headroom_minutes (it may be negative). Then cancel that change in Servicedesk (state cancelled); confirm it and check the saved change. Finally open Decision and record: budget_headroom_minutes (Error budget minus reserve minus the impact minutes of incidents charged to the SLO (may be negative)); cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); slo_id (Availability SLO consulted); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → reconcile two systems → write readback → structured decision
Graded answer fields: budget_headroom_minutes, cancelled_change_id, primary_engineer_id, service_id, slo_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 4.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.14
World digest: sha256:674a117d0386855a1febd9d24470139a6176df34e664a80606f27ba746fcd211
Package: sha256:2705718379ac5f53e4d5f86fd2578824f8a588aaf18390c044c0109c257e49a0 · 61 files · 5.6 MB · agent 30 min · verifier 5 min

70Change cancellation — Loyalty Service (us)wb-itsmdesk-itsmdesk-001-stale-advisory-c-e3d912-s8 · ITSMDesk · service operations coordinator · as of 2026-04-144 hops · 17 steps · 7 fields

Start in Servicedesk: find the service named “Loyalty Service (us)”. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. Open the service's availability SLO budget in Pulse and its incident list in Servicedesk: headroom = budget minutes minus reserve minutes minus the impact minutes of every incident charged to the SLO; report slo_id and budget_headroom_minutes (it may be negative). Then cancel that change in Servicedesk (state cancelled); confirm it and check the saved change. Finally open Decision and record: budget_headroom_minutes (Error budget minus reserve minus the impact minutes of incidents charged to the SLO (may be negative)); cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); slo_id (Availability SLO consulted); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → reconcile two systems → write readback → structured decision
Graded answer fields: budget_headroom_minutes, cancelled_change_id, primary_engineer_id, service_id, slo_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 4.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.14
World digest: sha256:b4268ea66016d9b7a37e59684d5c35ed9642774b483681e4d26dba6cdccc0337
Package: sha256:38917d17838e66298b4aea3732f8fa68ff539d01193153c58ac9c8e3fe6facc6 · 61 files · 5.6 MB · agent 30 min · verifier 5 min

71Change cancellation — Data Exporter (us)wb-itsmdesk-itsmdesk-001-stale-advisory-c-e3d912-s9 · ITSMDesk · service operations coordinator · as of 2026-04-144 hops · 17 steps · 7 fields

Start in Servicedesk: find the service named “Data Exporter (us)”. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. Open the service's availability SLO budget in Pulse and its incident list in Servicedesk: headroom = budget minutes minus reserve minutes minus the impact minutes of every incident charged to the SLO; report slo_id and budget_headroom_minutes (it may be negative). Then cancel that change in Servicedesk (state cancelled); confirm it and check the saved change. Finally open Decision and record: budget_headroom_minutes (Error budget minus reserve minus the impact minutes of incidents charged to the SLO (may be negative)); cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); slo_id (Availability SLO consulted); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → reconcile two systems → write readback → structured decision
Graded answer fields: budget_headroom_minutes, cancelled_change_id, primary_engineer_id, service_id, slo_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 4.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.14
World digest: sha256:a4b0fdf0d8b7b2abdb31f46faec2d658b4b23620315b2241325a83fc78d0d1ab
Package: sha256:254395da50cabb728bc724f359be239af6e5dae0eb15b30e31ad4787f9125f77 · 61 files · 5.7 MB · agent 30 min · verifier 5 min

72Planning pass — Data Exporter (us)wb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s0 · ITSMDesk · service operations coordinator · as of 2026-04-143 hops · 11 steps · 6 fields

Start in Servicedesk: find the service named “Data Exporter (us)”. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. In Servicedesk, add up impact_minutes over every incident on the service that was charged to the SLO; report charged_impact_minutes. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); charged_impact_minutes (Impact minutes of every incident charged to the SLO); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → aggregate paginated → structured decision
Graded answer fields: cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:e76f61aad2db296f03954788a04a700ce52457f7b1bf2fd53024e5c30a2a8196
Package: sha256:e59513357954e7c9d40276e4f732f612cc0adab00e178f8b234482ce395e79e9 · 61 files · 5.7 MB · agent 30 min · verifier 5 min

73Planning pass — Media Transcoder (v2)wb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s1 · ITSMDesk · service operations coordinator · as of 2026-04-143 hops · 11 steps · 6 fields

Start in Servicedesk: find the service named “Media Transcoder (v2)”. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. In Servicedesk, add up impact_minutes over every incident on the service that was charged to the SLO; report charged_impact_minutes. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); charged_impact_minutes (Impact minutes of every incident charged to the SLO); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → aggregate paginated → structured decision
Graded answer fields: cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:513b99e670aff9b7cbde455159f7890f3ba16014dcc78de0679880c95f3357fc
Package: sha256:967a4c7cc84ba37769890e9c325093d446406160e74910dcef02695a8736bc37 · 61 files · 5.7 MB · agent 30 min · verifier 5 min

74Planning pass — Risk Console (us)wb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s10 · ITSMDesk · service operations coordinator · as of 2026-04-143 hops · 11 steps · 6 fields

Start in Servicedesk: find the service named “Risk Console (us)”. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. In Servicedesk, add up impact_minutes over every incident on the service that was charged to the SLO; report charged_impact_minutes. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); charged_impact_minutes (Impact minutes of every incident charged to the SLO); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → aggregate paginated → structured decision
Graded answer fields: cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:bb8ff469fb4e24d1f9fffa57871f1d43c5c6182b42aa9739442962e44e14228a
Package: sha256:21b02a55f582916f6ca2c500d784b92ab91890cecb3dc081ce502c7a131e42eb · 61 files · 5.7 MB · agent 30 min · verifier 5 min

75Planning pass — Data Exporter (us)wb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s11 · ITSMDesk · service operations coordinator · as of 2026-04-143 hops · 11 steps · 6 fields

Hop classes: read key read → policy gated write → aggregate paginated → structured decision
Graded answer fields: cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:612b73efb03ca19b55cf2e2c86f8b8b702ad730c4beab07e018bf66bebee60bb
Package: sha256:6c13d4d6d6ffd2e85f60ff840f04b66b8530e43dff975fb2ebcf3bc7522105fb · 61 files · 5.7 MB · agent 30 min · verifier 5 min

76Planning pass — Identity Gateway (eu)wb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s2 · ITSMDesk · service operations coordinator · as of 2026-04-143 hops · 11 steps · 6 fields

Start in Servicedesk: find the service named “Identity Gateway (eu)”. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. In Servicedesk, add up impact_minutes over every incident on the service that was charged to the SLO; report charged_impact_minutes. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); charged_impact_minutes (Impact minutes of every incident charged to the SLO); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → aggregate paginated → structured decision
Graded answer fields: cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:1eb8f6c0739edf97827b0f71eb36e64070d8076090a9a6f836e49880ac985281
Package: sha256:00669c91d854ea6ace17d02ffd577ef1b3c2a8a2a146d759d6bd1f5db637b397 · 61 files · 5.7 MB · agent 30 min · verifier 5 min

77Planning pass — Session Store (legacy)wb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s3 · ITSMDesk · service operations coordinator · as of 2026-04-143 hops · 11 steps · 6 fields

Start in Servicedesk: find the service named “Session Store (legacy)”. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. In Servicedesk, add up impact_minutes over every incident on the service that was charged to the SLO; report charged_impact_minutes. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); charged_impact_minutes (Impact minutes of every incident charged to the SLO); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → aggregate paginated → structured decision
Graded answer fields: cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:a065631d6da1416debbef660d48c77dee03891720038623e23b704658e0cdb9f
Package: sha256:62c169f81f9235b60f2c3e1832b176c061f8d5ca3ea066436252c04991a52529 · 61 files · 5.7 MB · agent 30 min · verifier 5 min

78Planning pass — the service owned by Checkout in tier-2 with the code ledger-batchwb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s4 · ITSMDesk · service operations coordinator · as of 2026-04-143 hops · 11 steps · 6 fields

Start in Servicedesk: find the service owned by Checkout in tier-2 with the code ledger-batch. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. In Servicedesk, add up impact_minutes over every incident on the service that was charged to the SLO; report charged_impact_minutes. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); charged_impact_minutes (Impact minutes of every incident charged to the SLO); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → aggregate paginated → structured decision
Graded answer fields: cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.3 · page depth 3 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:67726c373fc47bd53480b9b1a59c7e9317f9c527179820d613c776d734f712df
Package: sha256:04c4ade70d111415fe2dbd630a30270c8e8acee5e3c4154ae96f30431b90d9c1 · 61 files · 5.7 MB · agent 30 min · verifier 5 min

79Planning pass — the service owned by Checkout in tier-1 with the code checkout-webwb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s5 · ITSMDesk · service operations coordinator · as of 2026-04-143 hops · 11 steps · 6 fields

Start in Servicedesk: find the service owned by Checkout in tier-1 with the code checkout-web. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. In Servicedesk, add up impact_minutes over every incident on the service that was charged to the SLO; report charged_impact_minutes. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); charged_impact_minutes (Impact minutes of every incident charged to the SLO); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → aggregate paginated → structured decision
Graded answer fields: cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.3 · page depth 3 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:21bc3190982583efd3fa67beb2710bcfe23c0329b0a1dd16bded37202b294fdd
Package: sha256:87cc52a61e5dee738d5c3e0ca03486d23082901fcb6c9190043d9187855e030a · 61 files · 5.7 MB · agent 30 min · verifier 5 min

80Planning pass — Inventory Sync (edge)wb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s6 · ITSMDesk · service operations coordinator · as of 2026-04-143 hops · 11 steps · 6 fields

Start in Servicedesk: find the service named “Inventory Sync (edge)”. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. In Servicedesk, add up impact_minutes over every incident on the service that was charged to the SLO; report charged_impact_minutes. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); charged_impact_minutes (Impact minutes of every incident charged to the SLO); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → aggregate paginated → structured decision
Graded answer fields: cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.3 · page depth 3 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:3ba03ae249066234b1474eb7ba2a6162dc2a35d127a567daae4c41c02db07f60
Package: sha256:17cf592479b9ae908bbbc3f8c8e7e4ebd6af5e9eb1a6d05649907704b89f3599 · 61 files · 5.7 MB · agent 30 min · verifier 5 min

81Planning pass — the service owned by Identity in tier-2 with the code risk-consolewb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s7 · ITSMDesk · service operations coordinator · as of 2026-04-143 hops · 11 steps · 6 fields

Start in Servicedesk: find the service owned by Identity in tier-2 with the code risk-console. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. In Servicedesk, add up impact_minutes over every incident on the service that was charged to the SLO; report charged_impact_minutes. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); charged_impact_minutes (Impact minutes of every incident charged to the SLO); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → aggregate paginated → structured decision
Graded answer fields: cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:c131cbe9f7c729ad945447e681488c8d08ad688d70777a629b24c23333aa4702
Package: sha256:6c19d69c0e909a7e15ebf768bef1a11fad1b4d3572e6cc989c476e04887684ed · 61 files · 5.7 MB · agent 30 min · verifier 5 min

82Planning pass — Payments API (legacy)wb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s8 · ITSMDesk · service operations coordinator · as of 2026-04-143 hops · 11 steps · 6 fields

Start in Servicedesk: find the service named “Payments API (legacy)”. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. In Servicedesk, add up impact_minutes over every incident on the service that was charged to the SLO; report charged_impact_minutes. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); charged_impact_minutes (Impact minutes of every incident charged to the SLO); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → aggregate paginated → structured decision
Graded answer fields: cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:ba3feda1b1b1fd066814c0cc0278bb2f8740e228422510859d7d94a4f52b4479
Package: sha256:a417b5e90e33e56789e8562aeb879ce556300dc553a486aa99d80089e70459ed · 61 files · 5.7 MB · agent 30 min · verifier 5 min

83Planning pass — Reporting Warehouse (legacy)wb-itsmdesk-itsmdesk-002-stale-advisory-c-a0436f-s9 · ITSMDesk · service operations coordinator · as of 2026-04-143 hops · 11 steps · 6 fields

Start in Servicedesk: find the service named “Reporting Warehouse (legacy)”. Open it and note the linked records. List the service's change requests in Servicedesk and, for each one not yet in implementation (new, assess, authorize or scheduled), check its advisory in Advisories: a change raised against a superseded advisory revision may not proceed (where several qualify, take the earliest opened). Report that change as cancelled_change_id and the superseded revision as superseded_advisory_id. In Servicedesk, add up impact_minutes over every incident on the service that was charged to the SLO; report charged_impact_minutes. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: cancelled_change_id (The service's earliest-opened change not yet in implementation that was raised against a superseded advisory revision); charged_impact_minutes (Impact minutes of every incident charged to the SLO); primary_engineer_id (The service's primary on-call engineer); service_id (Service the work relates to); superseded_advisory_id (The superseded advisory revision that change was raised against). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose needs_approval when an amount is outside the approval on file; choose cannot_proceed when the work cannot be done as briefed. In either of those cases set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → policy gated write → aggregate paginated → structured decision
Graded answer fields: cancelled_change_id, charged_impact_minutes, primary_engineer_id, service_id, superseded_advisory_id
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 6 answer_field · 0 expected writes
Difficulty: index 3.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:0e84f46af8ff3cd30f9b9e6753fdf316916410da0e5e8a1cbb0cb40fe719c3bb
Package: sha256:5a0c298f91a66b03cd5fce120963c8e2aea99dc4d24407460ce205920097decb · 61 files · 5.7 MB · agent 30 min · verifier 5 min

84Sprint assignment for Sable Ridge Groupwb-workplace-workplace-001-usable-capacity-0fe45e-s0 · Workplace · customer delivery coordinator · as of 2026-04-143 hops · 18 steps · 7 fields

Start in Deskline: find the open escalation for Sable Ridge Group. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 40” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on billing-engine (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing billing-engine that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → write readback → structured decision
Graded answer fields: assignee_id, escalation_id, issue_key, qualified_engineers, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.09
World digest: sha256:fb4a547f27869ec04fc537499669d25a1ff4431be05d4946d880006b631fca3b
Package: sha256:dce98d5cffb287acd599b3e28f3dcca7ac2437d5ccc7943c338020f131d94e6e · 61 files · 6.7 MB · agent 30 min · verifier 5 min

85Sprint assignment for Glenfield Partnerswb-workplace-workplace-001-usable-capacity-0fe45e-s1 · Workplace · customer delivery coordinator · as of 2026-04-143 hops · 18 steps · 7 fields

Start in Deskline: find the open escalation for Glenfield Partners about “Level-2 escalation”. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on mobile-sync (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing mobile-sync that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → write readback → structured decision
Graded answer fields: assignee_id, escalation_id, issue_key, qualified_engineers, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.09
World digest: sha256:59c760e64044dbe31c9e71ac9c093927418a3b94a12b05bd98240e5025a889b7
Package: sha256:d4e09dcd58dcc456b4ec7e13374a1ef2fc6218bcfca9ef76465fd17a784d6afd · 61 files · 6.8 MB · agent 30 min · verifier 5 min

86Sprint assignment for Pinecrest Mediawb-workplace-workplace-001-usable-capacity-0fe45e-s10 · Workplace · customer delivery coordinator · as of 2026-04-143 hops · 18 steps · 7 fields

Start in Deskline: find the open escalation for Pinecrest Media. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 35” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on document-pipeline (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing document-pipeline that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → write readback → structured decision
Graded answer fields: assignee_id, escalation_id, issue_key, qualified_engineers, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.09
World digest: sha256:2ac551d2c214ce9f575109e48d63c82160731fef2ab7e8374c34f3650b3a9132
Package: sha256:b0de2194d8e9655f57663172b35437ca9574dcb6c025019fc17523e128773be1 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

87Sprint assignment for Fairhaven Capitalwb-workplace-workplace-001-usable-capacity-0fe45e-s11 · Workplace · customer delivery coordinator · as of 2026-04-143 hops · 18 steps · 7 fields

Start in Deskline: find the open escalation for Fairhaven Capital. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on sso-identity (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing sso-identity that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → write readback → structured decision
Graded answer fields: assignee_id, escalation_id, issue_key, qualified_engineers, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.09
World digest: sha256:2e7a6da61d64fd41e3c30ce57aaafb413ee2a6a40c7cbb7e9edff8d2171e059f
Package: sha256:a3255d3974ce35275f955d7263003136318af24bd4636ca5cae6718d0b5ff045 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

88Sprint assignment for Tidewater Healthwb-workplace-workplace-001-usable-capacity-0fe45e-s2 · Workplace · customer delivery coordinator · as of 2026-04-143 hops · 18 steps · 7 fields

Start in Deskline: find the open escalation for Tidewater Health. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on document-pipeline (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing document-pipeline that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → write readback → structured decision
Graded answer fields: assignee_id, escalation_id, issue_key, qualified_engineers, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.09
World digest: sha256:40f57678bad93180ad096897af36bca5d3187eb894eeff00d25808ba0c0c5659
Package: sha256:62b5bd3bdfeef3a97f3ab158da9c2e08fe92a8237048d55ba8338c31de47828f · 61 files · 6.8 MB · agent 30 min · verifier 5 min

89Sprint assignment for Copperline Mediawb-workplace-workplace-001-usable-capacity-0fe45e-s3 · Workplace · customer delivery coordinator · as of 2026-04-143 hops · 18 steps · 7 fields

Start in Deskline: find the open escalation for Copperline Media. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 39” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on reporting-warehouse (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing reporting-warehouse that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → write readback → structured decision
Graded answer fields: assignee_id, escalation_id, issue_key, qualified_engineers, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.09
World digest: sha256:2caa4d71ec86a864c1739a30cdb4e34d14f41bf31583e198f7e3a112e4d0748f
Package: sha256:3f40cbccbcd3c9dcdbf0da828749fb782f897d88b549e2ce111d77bb3347adac · 61 files · 6.8 MB · agent 30 min · verifier 5 min

90Sprint assignment for Coldwater Insurancewb-workplace-workplace-001-usable-capacity-0fe45e-s4 · Workplace · customer delivery coordinator · as of 2026-04-143 hops · 18 steps · 7 fields

Start in Deskline: find the open escalation for Coldwater Insurance about “Dashboard latency”. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on billing-engine (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing billing-engine that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → write readback → structured decision
Graded answer fields: assignee_id, escalation_id, issue_key, qualified_engineers, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.09
World digest: sha256:4316a656005661f3f02838bd7fb8b97e3e319bc99e5045fc47c799e41c7998dd
Package: sha256:2a6caa45cac55add021775133e1b445e4857a0756677d7cf7a4e0d556d86cafd · 61 files · 6.8 MB · agent 30 min · verifier 5 min

91Sprint assignment for Bramblewood Capitalwb-workplace-workplace-001-usable-capacity-0fe45e-s5 · Workplace · customer delivery coordinator · as of 2026-04-143 hops · 18 steps · 7 fields

Start in Deskline: find the open escalation for Bramblewood Capital. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on integrations-api (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing integrations-api that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → write readback → structured decision
Graded answer fields: assignee_id, escalation_id, issue_key, qualified_engineers, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.09
World digest: sha256:ae8e38c627213d7b4fc599baf6118b0402ba6c05fd0d2b585add027c1c8463cc
Package: sha256:e8f65cbcede2f5c2ce3470dc6fe092887cc88755e0f8cfe67e690129d663f59d · 61 files · 6.8 MB · agent 30 min · verifier 5 min

92Sprint assignment for Wrenfield Groupwb-workplace-workplace-001-usable-capacity-0fe45e-s6 · Workplace · customer delivery coordinator · as of 2026-04-143 hops · 18 steps · 7 fields

Start in Deskline: find the open escalation for Wrenfield Group. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 36” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on mobile-sync (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing mobile-sync that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → write readback → structured decision
Graded answer fields: assignee_id, escalation_id, issue_key, qualified_engineers, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.09
World digest: sha256:4f55e1ee24e700bf532661172660deddadb32fede9090e88f6ff50f59d05834c
Package: sha256:c7c09e8b5f00538c841d28300c590e86ff0ff8cd406f166cf783674c7c5ae926 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

93Sprint assignment for Thornbury Healthwb-workplace-workplace-001-usable-capacity-0fe45e-s7 · Workplace · customer delivery coordinator · as of 2026-04-143 hops · 18 steps · 7 fields

Start in Deskline: find the open escalation for Thornbury Health. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 31” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on payments-gateway (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing payments-gateway that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → write readback → structured decision
Graded answer fields: assignee_id, escalation_id, issue_key, qualified_engineers, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.09
World digest: sha256:a1c1b8312297aede01fdc310bf4d03ee7e77f818f52511caf64a141659e4dc55
Package: sha256:b3d08609d72cdbc643cf594e614ca3ee7ba2bd950e86b998278f695173ad3019 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

94Sprint assignment for Marlowewb-workplace-workplace-001-usable-capacity-0fe45e-s8 · Workplace · customer delivery coordinator · as of 2026-04-143 hops · 18 steps · 7 fields

Start in Deskline: find the open escalation for Marlowe. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 36” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on billing-engine (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing billing-engine that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → write readback → structured decision
Graded answer fields: assignee_id, escalation_id, issue_key, qualified_engineers, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.09
World digest: sha256:589bd32b36834874017650e50186fb43b44e860e827062df1c4edb1b507cb5fd
Package: sha256:c687a4989fa413e705d8d974540fd30603a795e3519c315ae69756c372526251 · 61 files · 6.7 MB · agent 30 min · verifier 5 min

95Sprint assignment for Amberly Partnerswb-workplace-workplace-001-usable-capacity-0fe45e-s9 · Workplace · customer delivery coordinator · as of 2026-04-143 hops · 18 steps · 7 fields

Start in Deskline: find the open escalation for Amberly Partners. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on billing-engine (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing billing-engine that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → write readback → structured decision
Graded answer fields: assignee_id, escalation_id, issue_key, qualified_engineers, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 7 answer_field · 1 expected writes
Difficulty: index 3.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.09
World digest: sha256:8e57370fec70273f739695932e43a97c4dfcd6bdbd2de360ddd2358e877f9c0b
Package: sha256:9ea304c013e2cebce286c76e8e19dc651022298f9372c9695a964a517751f4c1 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

96Session booking for Brackenridge Groupwb-workplace-workplace-001-usable-capacity-391148-s0 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 26 steps · 10 fields

Start in Deskline: find the open escalation for Brackenridge Group. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on document-pipeline (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing document-pipeline that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on document-pipeline (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Then book that session in Rota for the escalation from the start of the block, citing the escalation id in the description; confirm it and check the saved booking. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); booking_id (Identifier of the booking saved); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → capacity computation → write readback → structured decision
Graded answer fields: assignee_id, booking_id, employee_id, escalation_id, issue_key, qualified_engineers, session_date, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 10 answer_field · 6 expected writes
Difficulty: index 4.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.09
World digest: sha256:fb4a547f27869ec04fc537499669d25a1ff4431be05d4946d880006b631fca3b
Package: sha256:625289ebd44ec487bc67a2aeca683f7f91595fadf623f79345de95b878cb25c9 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

97Session booking for Thornbury Logisticswb-workplace-workplace-001-usable-capacity-391148-s1 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 26 steps · 10 fields

Start in Deskline: find the open escalation for Thornbury Logistics. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on document-pipeline (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing document-pipeline that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on document-pipeline (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Then book that session in Rota for the escalation from the start of the block, citing the escalation id in the description; confirm it and check the saved booking. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); booking_id (Identifier of the booking saved); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → capacity computation → write readback → structured decision
Graded answer fields: assignee_id, booking_id, employee_id, escalation_id, issue_key, qualified_engineers, session_date, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 10 answer_field · 7 expected writes
Difficulty: index 4.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.09
World digest: sha256:59c760e64044dbe31c9e71ac9c093927418a3b94a12b05bd98240e5025a889b7
Package: sha256:77d7d8049da440670e2deae20a683d66a1b4c9c72ec9a63c51c7d406f9d977eb · 61 files · 6.8 MB · agent 30 min · verifier 5 min

98Session booking for Harrowgate Foodswb-workplace-workplace-001-usable-capacity-391148-s10 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 22 steps · 7 fields

Start in Deskline: find the open escalation for Harrowgate Foods. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 35” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on data-migration (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on data-migration (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. Then book that session in Rota for the escalation from the start of the block, citing the escalation id in the description; confirm it and check the saved booking. Finally open Decision and record: booking_id (Identifier of the booking saved); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → capacity computation → write readback → structured decision
Graded answer fields: booking_id, employee_id, escalation_id, qualified_engineers, session_date, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 7 answer_field · 8 expected writes
Difficulty: index 4.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.13
World digest: sha256:2ac551d2c214ce9f575109e48d63c82160731fef2ab7e8374c34f3650b3a9132
Package: sha256:976ac6a489e479d8580d1a040778bc3562cdf7bc556ddd14823805e0fbf7515a · 61 files · 6.8 MB · agent 30 min · verifier 5 min

99Session booking for Copperline Insurancewb-workplace-workplace-001-usable-capacity-391148-s11 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 26 steps · 10 fields

Start in Deskline: find the open escalation for Copperline Insurance. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on payments-gateway (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing payments-gateway that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on payments-gateway (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Then book that session in Rota for the escalation from the start of the block, citing the escalation id in the description; confirm it and check the saved booking. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); booking_id (Identifier of the booking saved); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → capacity computation → write readback → structured decision
Graded answer fields: assignee_id, booking_id, employee_id, escalation_id, issue_key, qualified_engineers, session_date, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 10 answer_field · 9 expected writes
Difficulty: index 4.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.09
World digest: sha256:2e7a6da61d64fd41e3c30ce57aaafb413ee2a6a40c7cbb7e9edff8d2171e059f
Package: sha256:3f6a97cb9c1a970dc4ce23529c1dca548237c952be59be168bc810bd2bfb4f7e · 61 files · 6.8 MB · agent 30 min · verifier 5 min

100Session booking for Halcyon Systemswb-workplace-workplace-001-usable-capacity-391148-s2 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 26 steps · 10 fields

Start in Deskline: find the open escalation for Halcyon Systems about “Systems mobile”. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on integrations-api (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing integrations-api that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on integrations-api (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Then book that session in Rota for the escalation from the start of the block, citing the escalation id in the description; confirm it and check the saved booking. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); booking_id (Identifier of the booking saved); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → capacity computation → write readback → structured decision
Graded answer fields: assignee_id, booking_id, employee_id, escalation_id, issue_key, qualified_engineers, session_date, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 10 answer_field · 9 expected writes
Difficulty: index 4.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.09
World digest: sha256:40f57678bad93180ad096897af36bca5d3187eb894eeff00d25808ba0c0c5659
Package: sha256:7c148b4f93dd1d51b4be80b37445000df23e0a07bd2a344e8ebbd593048d1d1e · 61 files · 6.8 MB · agent 30 min · verifier 5 min

101Session booking for Meridian Mediawb-workplace-workplace-001-usable-capacity-391148-s3 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 22 steps · 7 fields

Start in Deskline: find the open escalation for Meridian Media about “Media dashboard”. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on data-migration (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on data-migration (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. Then book that session in Rota for the escalation from the start of the block, citing the escalation id in the description; confirm it and check the saved booking. Finally open Decision and record: booking_id (Identifier of the booking saved); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → capacity computation → write readback → structured decision
Graded answer fields: booking_id, employee_id, escalation_id, qualified_engineers, session_date, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 7 answer_field · 8 expected writes
Difficulty: index 4.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.13
World digest: sha256:2caa4d71ec86a864c1739a30cdb4e34d14f41bf31583e198f7e3a112e4d0748f
Package: sha256:44156a2e097b39b53b18f72fbcc312cf00f74f42e7365f24bf9eb09c996eaff0 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

102Session booking for Amberly Logisticswb-workplace-workplace-001-usable-capacity-391148-s5 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 26 steps · 10 fields

Start in Deskline: find the open escalation for Amberly Logistics about “Payment reconciliation”. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on billing-engine (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing billing-engine that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on billing-engine (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Then book that session in Rota for the escalation from the start of the block, citing the escalation id in the description; confirm it and check the saved booking. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); booking_id (Identifier of the booking saved); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → capacity computation → write readback → structured decision
Graded answer fields: assignee_id, booking_id, employee_id, escalation_id, issue_key, qualified_engineers, session_date, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 10 answer_field · 9 expected writes
Difficulty: index 4.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.09
World digest: sha256:ae8e38c627213d7b4fc599baf6118b0402ba6c05fd0d2b585add027c1c8463cc
Package: sha256:6b042923aacd08c65a4210e0dcbf30a7156da699fd660671b6abb4468152927e · 61 files · 6.8 MB · agent 30 min · verifier 5 min

103Session booking for Oakhaven Logisticswb-workplace-workplace-001-usable-capacity-391148-s6 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 26 steps · 10 fields

Start in Deskline: find the open escalation for Oakhaven Logistics. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 34” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on billing-engine (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing billing-engine that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on billing-engine (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Then book that session in Rota for the escalation from the start of the block, citing the escalation id in the description; confirm it and check the saved booking. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); booking_id (Identifier of the booking saved); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → capacity computation → write readback → structured decision
Graded answer fields: assignee_id, booking_id, employee_id, escalation_id, issue_key, qualified_engineers, session_date, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 10 answer_field · 4 expected writes
Difficulty: index 4.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.09
World digest: sha256:4f55e1ee24e700bf532661172660deddadb32fede9090e88f6ff50f59d05834c
Package: sha256:103ebfc28ef6cee4cce25a27539cd649662c6d8fd74c2b8dc0b0c28ef91cd227 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

104Session booking for Glenfield Healthwb-workplace-workplace-001-usable-capacity-391148-s7 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 26 steps · 10 fields

Start in Deskline: find the open escalation for Glenfield Health about “Glenfield Health”. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 31” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on data-migration (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing data-migration that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on data-migration (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Then book that session in Rota for the escalation from the start of the block, citing the escalation id in the description; confirm it and check the saved booking. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); booking_id (Identifier of the booking saved); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → capacity computation → write readback → structured decision
Graded answer fields: assignee_id, booking_id, employee_id, escalation_id, issue_key, qualified_engineers, session_date, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 10 answer_field · 9 expected writes
Difficulty: index 4.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.09
World digest: sha256:a1c1b8312297aede01fdc310bf4d03ee7e77f818f52511caf64a141659e4dc55
Package: sha256:6448e38f5ad841b6abc28caf31c24896b9ab4bebb99f08336790748a45af8db9 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

105Session booking for Sable Ridge Insurancewb-workplace-workplace-001-usable-capacity-391148-s8 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 22 steps · 7 fields

Start in Deskline: find the open escalation for Sable Ridge Insurance about “Level-2 escalation”. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on document-pipeline (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on document-pipeline (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. Then book that session in Rota for the escalation from the start of the block, citing the escalation id in the description; confirm it and check the saved booking. Finally open Decision and record: booking_id (Identifier of the booking saved); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → capacity computation → write readback → structured decision
Graded answer fields: booking_id, employee_id, escalation_id, qualified_engineers, session_date, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 7 answer_field · 6 expected writes
Difficulty: index 4.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.13
World digest: sha256:589bd32b36834874017650e50186fb43b44e860e827062df1c4edb1b507cb5fd
Package: sha256:2c7bc6411d37af27ac6bc2bb6441de79147c8f3bb751fc5852d7f40fa9495c29 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

106Session booking for Westbrook Foodswb-workplace-workplace-001-usable-capacity-391148-s9 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 26 steps · 10 fields

Start in Deskline: find the open escalation for Westbrook Foods. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 31” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on sso-identity (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing sso-identity that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on sso-identity (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Then book that session in Rota for the escalation from the start of the block, citing the escalation id in the description; confirm it and check the saved booking. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); booking_id (Identifier of the booking saved); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → capacity computation → write readback → structured decision
Graded answer fields: assignee_id, booking_id, employee_id, escalation_id, issue_key, qualified_engineers, session_date, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 3 evidence_read · 10 answer_field · 9 expected writes
Difficulty: index 4.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.09
World digest: sha256:8e57370fec70273f739695932e43a97c4dfcd6bdbd2de360ddd2358e877f9c0b
Package: sha256:9b453b9cad5adb8d6cccdfb1b440f093acfc3f6534e1b25677fb07d6974e41db · 61 files · 6.8 MB · agent 30 min · verifier 5 min

107Planning pass for Amberly Holdingswb-workplace-workplace-001-usable-capacity-48c383-s0 · Workplace · customer delivery coordinator · as of 2026-04-142 hops · 14 steps · 4 fields

Start in Deskline: find the open escalation for Amberly Holdings. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 40” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on data-migration (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: escalation_id (Escalation the work relates to); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → structured decision
Graded answer fields: escalation_id, qualified_engineers, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 4 answer_field · 0 expected writes
Difficulty: index 2.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:fb4a547f27869ec04fc537499669d25a1ff4431be05d4946d880006b631fca3b
Package: sha256:1cabb9645d1de6230c3017f7714310b22c35131e67bd14533846af6f2631462f · 61 files · 6.7 MB · agent 30 min · verifier 5 min

108Planning pass for Oakhaven Labswb-workplace-workplace-001-usable-capacity-48c383-s1 · Workplace · customer delivery coordinator · as of 2026-04-142 hops · 14 steps · 7 fields

Start in Deskline: find the open escalation for Oakhaven Labs. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on payments-gateway (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing payments-gateway that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → structured decision
Graded answer fields: assignee_id, escalation_id, issue_key, qualified_engineers, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 7 answer_field · 0 expected writes
Difficulty: index 2.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.13
World digest: sha256:59c760e64044dbe31c9e71ac9c093927418a3b94a12b05bd98240e5025a889b7
Package: sha256:a9e025d16085d967e9d930224ecb4352d8a25e6d9c8afc0dffec95f9f36434e2 · 61 files · 6.7 MB · agent 30 min · verifier 5 min

109Planning pass for Pinecrest Mediawb-workplace-workplace-001-usable-capacity-48c383-s10 · Workplace · customer delivery coordinator · as of 2026-04-142 hops · 14 steps · 7 fields

Start in Deskline: find the open escalation for Pinecrest Media. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 35” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on document-pipeline (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing document-pipeline that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → structured decision
Graded answer fields: assignee_id, escalation_id, issue_key, qualified_engineers, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 7 answer_field · 0 expected writes
Difficulty: index 2.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.13
World digest: sha256:2ac551d2c214ce9f575109e48d63c82160731fef2ab7e8374c34f3650b3a9132
Package: sha256:543a66a80077889a8d6113282eea69bf57792dc3f4b728a2a3b97c7ea5498388 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

110Planning pass for Hollins Energywb-workplace-workplace-001-usable-capacity-48c383-s11 · Workplace · customer delivery coordinator · as of 2026-04-142 hops · 14 steps · 4 fields

Start in Deskline: find the open escalation for Hollins Energy. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 31” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on billing-engine (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: escalation_id (Escalation the work relates to); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → structured decision
Graded answer fields: escalation_id, qualified_engineers, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 4 answer_field · 0 expected writes
Difficulty: index 2.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:2e7a6da61d64fd41e3c30ce57aaafb413ee2a6a40c7cbb7e9edff8d2171e059f
Package: sha256:82cb6d743e0572f0a60bcd08a293638601acb9171c07ecc22f8ea08c35af626a · 61 files · 6.7 MB · agent 30 min · verifier 5 min

111Planning pass for Harrowgate Groupwb-workplace-workplace-001-usable-capacity-48c383-s2 · Workplace · customer delivery coordinator · as of 2026-04-142 hops · 14 steps · 7 fields

Start in Deskline: find the open escalation for Harrowgate Group. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on document-pipeline (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing document-pipeline that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → structured decision
Graded answer fields: assignee_id, escalation_id, issue_key, qualified_engineers, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 7 answer_field · 0 expected writes
Difficulty: index 2.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.13
World digest: sha256:40f57678bad93180ad096897af36bca5d3187eb894eeff00d25808ba0c0c5659
Package: sha256:f9ac95abf65bcd4a107063258ae5d76bfd32eb3de86cf4ee5852da24d9c182ce · 61 files · 6.7 MB · agent 30 min · verifier 5 min

112Planning pass for Thornbury Capitalwb-workplace-workplace-001-usable-capacity-48c383-s3 · Workplace · customer delivery coordinator · as of 2026-04-142 hops · 14 steps · 4 fields

Start in Deskline: find the open escalation for Thornbury Capital. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on data-migration (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: escalation_id (Escalation the work relates to); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → structured decision
Graded answer fields: escalation_id, qualified_engineers, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 4 answer_field · 0 expected writes
Difficulty: index 2.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:2caa4d71ec86a864c1739a30cdb4e34d14f41bf31583e198f7e3a112e4d0748f
Package: sha256:203384d34985236fbe11c9e0820ac92539dc5b538d55a22875754f41065a9717 · 61 files · 6.7 MB · agent 30 min · verifier 5 min

113Planning pass for Wrenfield Groupwb-workplace-workplace-001-usable-capacity-48c383-s6 · Workplace · customer delivery coordinator · as of 2026-04-142 hops · 14 steps · 7 fields

Start in Deskline: find the open escalation for Wrenfield Group. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 36” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on mobile-sync (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing mobile-sync that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → structured decision
Graded answer fields: assignee_id, escalation_id, issue_key, qualified_engineers, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 7 answer_field · 0 expected writes
Difficulty: index 2.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.13
World digest: sha256:4f55e1ee24e700bf532661172660deddadb32fede9090e88f6ff50f59d05834c
Package: sha256:a0681dffdaefb150fa4f32aaa6d4641aaacfdc41f05d61952dad629ed9924377 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

114Planning pass for Sable Ridge Insurancewb-workplace-workplace-001-usable-capacity-48c383-s8 · Workplace · customer delivery coordinator · as of 2026-04-142 hops · 14 steps · 4 fields

Start in Deskline: find the open escalation for Sable Ridge Insurance about “Level-2 escalation”. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on document-pipeline (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: escalation_id (Escalation the work relates to); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → structured decision
Graded answer fields: escalation_id, qualified_engineers, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 2 evidence_read · 4 answer_field · 0 expected writes
Difficulty: index 2.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.20
World digest: sha256:589bd32b36834874017650e50186fb43b44e860e827062df1c4edb1b507cb5fd
Package: sha256:14c5cde06da96f028ff7d7b0eff15dd4af614b4a7f1a18abacba00fb77d06f08 · 61 files · 6.7 MB · agent 30 min · verifier 5 min

115Session booking for Copperline Energywb-workplace-workplace-001-usable-capacity-87d413-s0 · Workplace · customer delivery coordinator · as of 2026-04-145 hops · 27 steps · 11 fields

Start in Deskline: find the open escalation for Copperline Energy about “Copperline Energy”. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 40” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on integrations-api (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing integrations-api that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on integrations-api (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. Add up the story points still open (To Do, In Progress or In Review) across every issue in that sprint; report sprint_open_points. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Then book that session in Rota for the escalation from the start of the block, citing the escalation id in the description; confirm it and check the saved booking. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); booking_id (Identifier of the booking saved); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); sprint_open_points (Story points still open across every issue in the sprint); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: assignee_id, booking_id, employee_id, escalation_id, issue_key, qualified_engineers, session_date, sprint_id, sprint_open_points, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 11 answer_field · 9 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.11
World digest: sha256:fb4a547f27869ec04fc537499669d25a1ff4431be05d4946d880006b631fca3b
Package: sha256:f8651cb7702d2e67a0cc805093a5a66bb8c01806b9547b5337413c7a604ba09f · 61 files · 6.8 MB · agent 30 min · verifier 5 min

116Session booking for Halcyon Logisticswb-workplace-workplace-001-usable-capacity-87d413-s1 · Workplace · customer delivery coordinator · as of 2026-04-145 hops · 27 steps · 11 fields

Start in Deskline: find the open escalation for Halcyon Logistics. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on payments-gateway (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing payments-gateway that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on payments-gateway (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. Add up the story points still open (To Do, In Progress or In Review) across every issue in that sprint; report sprint_open_points. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Then book that session in Rota for the escalation from the start of the block, citing the escalation id in the description; confirm it and check the saved booking. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); booking_id (Identifier of the booking saved); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); sprint_open_points (Story points still open across every issue in the sprint); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: assignee_id, booking_id, employee_id, escalation_id, issue_key, qualified_engineers, session_date, sprint_id, sprint_open_points, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 11 answer_field · 7 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.11
World digest: sha256:59c760e64044dbe31c9e71ac9c093927418a3b94a12b05bd98240e5025a889b7
Package: sha256:a4670aee8204bc8da551d31a9307fc2bc15718cf8ebe1b3408911bbe5d1bf4db · 61 files · 6.8 MB · agent 30 min · verifier 5 min

117Session booking for Harrowgate Partnerswb-workplace-workplace-001-usable-capacity-87d413-s10 · Workplace · customer delivery coordinator · as of 2026-04-145 hops · 27 steps · 11 fields

Start in Deskline: find the open escalation for Harrowgate Partners. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 35” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on data-migration (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing data-migration that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on data-migration (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. Add up the story points still open (To Do, In Progress or In Review) across every issue in that sprint; report sprint_open_points. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Then book that session in Rota for the escalation from the start of the block, citing the escalation id in the description; confirm it and check the saved booking. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); booking_id (Identifier of the booking saved); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); sprint_open_points (Story points still open across every issue in the sprint); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: assignee_id, booking_id, employee_id, escalation_id, issue_key, qualified_engineers, session_date, sprint_id, sprint_open_points, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 11 answer_field · 9 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.11
World digest: sha256:2ac551d2c214ce9f575109e48d63c82160731fef2ab7e8374c34f3650b3a9132
Package: sha256:5c70972e283ec7c1817673010fc88af8166eec1cac3d8d16687d616d8f3fbbe2 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

118Session booking for Copperline Groupwb-workplace-workplace-001-usable-capacity-87d413-s11 · Workplace · customer delivery coordinator · as of 2026-04-145 hops · 27 steps · 11 fields

Start in Deskline: find the open escalation for Copperline Group. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on mobile-sync (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing mobile-sync that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on mobile-sync (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. Add up the story points still open (To Do, In Progress or In Review) across every issue in that sprint; report sprint_open_points. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Then book that session in Rota for the escalation from the start of the block, citing the escalation id in the description; confirm it and check the saved booking. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); booking_id (Identifier of the booking saved); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); sprint_open_points (Story points still open across every issue in the sprint); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: assignee_id, booking_id, employee_id, escalation_id, issue_key, qualified_engineers, session_date, sprint_id, sprint_open_points, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 11 answer_field · 9 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.11
World digest: sha256:2e7a6da61d64fd41e3c30ce57aaafb413ee2a6a40c7cbb7e9edff8d2171e059f
Package: sha256:78e5ff78153171bc795fb8bc6dd0c27148efc27da7495622991540631ed27ef1 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

119Session booking for Halcyon Systemswb-workplace-workplace-001-usable-capacity-87d413-s2 · Workplace · customer delivery coordinator · as of 2026-04-145 hops · 27 steps · 11 fields

Start in Deskline: find the open escalation for Halcyon Systems about “Systems mobile”. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on integrations-api (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing integrations-api that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on integrations-api (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. Add up the story points still open (To Do, In Progress or In Review) across every issue in that sprint; report sprint_open_points. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Then book that session in Rota for the escalation from the start of the block, citing the escalation id in the description; confirm it and check the saved booking. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); booking_id (Identifier of the booking saved); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); sprint_open_points (Story points still open across every issue in the sprint); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: assignee_id, booking_id, employee_id, escalation_id, issue_key, qualified_engineers, session_date, sprint_id, sprint_open_points, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 11 answer_field · 9 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.11
World digest: sha256:40f57678bad93180ad096897af36bca5d3187eb894eeff00d25808ba0c0c5659
Package: sha256:03d6c9488af235916f1a1ab7e474c8a1fa352ef05dcbfa85a9bfc0cd83fdffa6 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

120Session booking for Glenfield Logisticswb-workplace-workplace-001-usable-capacity-87d413-s3 · Workplace · customer delivery coordinator · as of 2026-04-145 hops · 27 steps · 11 fields

Start in Deskline: find the open escalation for Glenfield Logistics. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on mobile-sync (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing mobile-sync that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on mobile-sync (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. Add up the story points still open (To Do, In Progress or In Review) across every issue in that sprint; report sprint_open_points. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Then book that session in Rota for the escalation from the start of the block, citing the escalation id in the description; confirm it and check the saved booking. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); booking_id (Identifier of the booking saved); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); sprint_open_points (Story points still open across every issue in the sprint); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: assignee_id, booking_id, employee_id, escalation_id, issue_key, qualified_engineers, session_date, sprint_id, sprint_open_points, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 11 answer_field · 7 expected writes
Difficulty: index 5.2 · page depth 2 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.11
World digest: sha256:2caa4d71ec86a864c1739a30cdb4e34d14f41bf31583e198f7e3a112e4d0748f
Package: sha256:b7d9838421844288cd92caecace3d018faf883bae33828b72550ab1b1a85fc02 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

121Session booking for Hollins Capitalwb-workplace-workplace-001-usable-capacity-87d413-s5 · Workplace · customer delivery coordinator · as of 2026-04-145 hops · 27 steps · 11 fields

Start in Deskline: find the open escalation for Hollins Capital about “on audit”. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on sso-identity (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing sso-identity that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on sso-identity (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. Add up the story points still open (To Do, In Progress or In Review) across every issue in that sprint; report sprint_open_points. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Then book that session in Rota for the escalation from the start of the block, citing the escalation id in the description; confirm it and check the saved booking. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); booking_id (Identifier of the booking saved); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); sprint_open_points (Story points still open across every issue in the sprint); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: assignee_id, booking_id, employee_id, escalation_id, issue_key, qualified_engineers, session_date, sprint_id, sprint_open_points, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 11 answer_field · 9 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.11
World digest: sha256:ae8e38c627213d7b4fc599baf6118b0402ba6c05fd0d2b585add027c1c8463cc
Package: sha256:8c91e612829b26fdb5943ac58447f2a56d7c4463aefe5bfe6713b9d439429b69 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

122Session booking for Glenfield Insurancewb-workplace-workplace-001-usable-capacity-87d413-s6 · Workplace · customer delivery coordinator · as of 2026-04-145 hops · 27 steps · 11 fields

Start in Deskline: find the open escalation for Glenfield Insurance about “Glenfield escalation”. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 36” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on data-migration (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing data-migration that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on data-migration (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. Add up the story points still open (To Do, In Progress or In Review) across every issue in that sprint; report sprint_open_points. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Then book that session in Rota for the escalation from the start of the block, citing the escalation id in the description; confirm it and check the saved booking. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); booking_id (Identifier of the booking saved); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); sprint_open_points (Story points still open across every issue in the sprint); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: assignee_id, booking_id, employee_id, escalation_id, issue_key, qualified_engineers, session_date, sprint_id, sprint_open_points, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 11 answer_field · 9 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.11
World digest: sha256:4f55e1ee24e700bf532661172660deddadb32fede9090e88f6ff50f59d05834c
Package: sha256:84b9d05b9f8e43e47a91652e322a57b55ae6aa7893a617722dce3980dc6daad6 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

123Session booking for Eastmoor Healthwb-workplace-workplace-001-usable-capacity-87d413-s7 · Workplace · customer delivery coordinator · as of 2026-04-145 hops · 27 steps · 11 fields

Start in Deskline: find the open escalation for Eastmoor Health about “Level-1 escalation”. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 31” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on reporting-warehouse (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing reporting-warehouse that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on reporting-warehouse (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. Add up the story points still open (To Do, In Progress or In Review) across every issue in that sprint; report sprint_open_points. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Then book that session in Rota for the escalation from the start of the block, citing the escalation id in the description; confirm it and check the saved booking. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); booking_id (Identifier of the booking saved); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); sprint_open_points (Story points still open across every issue in the sprint); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: assignee_id, booking_id, employee_id, escalation_id, issue_key, qualified_engineers, session_date, sprint_id, sprint_open_points, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 11 answer_field · 9 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.11
World digest: sha256:a1c1b8312297aede01fdc310bf4d03ee7e77f818f52511caf64a141659e4dc55
Package: sha256:a9f87c2340de755d0998597a46fd6b58d1424ddc8e4dea305edf2c1ab4c8af44 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

124Session booking for Redcliffe Insurancewb-workplace-workplace-001-usable-capacity-87d413-s8 · Workplace · customer delivery coordinator · as of 2026-04-145 hops · 27 steps · 11 fields

Start in Deskline: find the open escalation for Redcliffe Insurance about “Redcliffe escalation”. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on billing-engine (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing billing-engine that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on billing-engine (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. Add up the story points still open (To Do, In Progress or In Review) across every issue in that sprint; report sprint_open_points. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Then book that session in Rota for the escalation from the start of the block, citing the escalation id in the description; confirm it and check the saved booking. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); booking_id (Identifier of the booking saved); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); sprint_open_points (Story points still open across every issue in the sprint); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: assignee_id, booking_id, employee_id, escalation_id, issue_key, qualified_engineers, session_date, sprint_id, sprint_open_points, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 11 answer_field · 8 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.11
World digest: sha256:589bd32b36834874017650e50186fb43b44e860e827062df1c4edb1b507cb5fd
Package: sha256:acf464dc7d40046ffcd9c19a9a4eca1a76130e534d501db8a14671b37d67bb4b · 61 files · 6.8 MB · agent 30 min · verifier 5 min

125Session booking for Stanmere Holdingswb-workplace-workplace-001-usable-capacity-87d413-s9 · Workplace · customer delivery coordinator · as of 2026-04-145 hops · 27 steps · 11 fields

Start in Deskline: find the open escalation for Stanmere Holdings. Open it and note the linked records. In Sprintboard, find the active sprint named “Sprint 31” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on mobile-sync (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing mobile-sync that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on mobile-sync (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. Add up the story points still open (To Do, In Progress or In Review) across every issue in that sprint; report sprint_open_points. Then move that issue into the sprint and assign it to that engineer in Sprintboard; confirm it and check the saved issue. Then book that session in Rota for the escalation from the start of the block, citing the escalation id in the description; confirm it and check the saved booking. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); booking_id (Identifier of the booking saved); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); sprint_open_points (Story points still open across every issue in the sprint); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → reconcile two systems → capacity computation → aggregate paginated → write readback → structured decision
Graded answer fields: assignee_id, booking_id, employee_id, escalation_id, issue_key, qualified_engineers, session_date, sprint_id, sprint_open_points, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 11 answer_field · 9 expected writes
Difficulty: index 5.1 · page depth 1 · hazards none · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.11
World digest: sha256:8e57370fec70273f739695932e43a97c4dfcd6bdbd2de360ddd2358e877f9c0b
Package: sha256:8f365ad997b63d07a9ceeddb99db91abdb7baa7d6989119461c9739669b21f67 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

126Planning pass for Marlowe Mediawb-workplace-workplace-002-open-points-84278e-s0 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 19 steps · 10 fields

Start in Deskline: find the escalation for Marlowe Media about “Marlowe SSO”. Open it and note the linked records. In Sprintboard, add up the story points of every linked issue in To Do / In Progress / In Review, regardless of issue type (a spike or chore counts like a fix); report the total as required_points. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on document-pipeline (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on document-pipeline (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing document-pipeline that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); required_points (Story points of every issue linked to the escalation that is in To Do, In Progress or In Review, regardless of issue type); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → capacity computation → reconcile two systems → structured decision
Graded answer fields: assignee_id, employee_id, escalation_id, issue_key, qualified_engineers, required_points, session_date, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 10 answer_field · 0 expected writes
Difficulty: index 5 · page depth 5 · hazards pagination_depth · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:13ee338c912e44594142cc964a084da9ebaaff7ce4c469a718528e3a8bcd6254
Package: sha256:422cf9429a00f0b47bb84f753d5489f43c2c9f06b39f17aa3b583af94779c5b9 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

127Planning pass for Silverbeckwb-workplace-workplace-002-open-points-84278e-s1 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 19 steps · 10 fields

Start in Deskline: find the escalation for Silverbeck. Open it and note the linked records. In Sprintboard, add up the story points of every linked issue in To Do / In Progress / In Review, regardless of issue type (a spike or chore counts like a fix); report the total as required_points. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on document-pipeline (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. In Sprintboard, find the active sprint named “Sprint 38” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on document-pipeline (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing document-pipeline that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); required_points (Story points of every issue linked to the escalation that is in To Do, In Progress or In Review, regardless of issue type); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → capacity computation → reconcile two systems → structured decision
Graded answer fields: assignee_id, employee_id, escalation_id, issue_key, qualified_engineers, required_points, session_date, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 10 answer_field · 0 expected writes
Difficulty: index 5.1 · page depth 6 · hazards pagination_depth · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:6e87c9ddb32c081e5b60eb0d3034e5e13b3af37a5ef471b8a7f52f61d67b18a8
Package: sha256:a47bdebe869397f0bcb3032375318cc7089b146b6586dcac690f45f9e668d3f7 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

128Planning pass for Oakhaven Holdingswb-workplace-workplace-002-open-points-84278e-s10 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 18 steps · 10 fields

Start in Deskline: find the escalation for Oakhaven Holdings. Open it and note the linked records. In Sprintboard, add up the story points of every linked issue in To Do / In Progress / In Review, regardless of issue type (a spike or chore counts like a fix); report the total as required_points. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on payments-gateway (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on payments-gateway (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing payments-gateway that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); required_points (Story points of every issue linked to the escalation that is in To Do, In Progress or In Review, regardless of issue type); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → capacity computation → reconcile two systems → structured decision
Graded answer fields: assignee_id, employee_id, escalation_id, issue_key, qualified_engineers, required_points, session_date, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 10 answer_field · 0 expected writes
Difficulty: index 5 · page depth 5 · hazards pagination_depth · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:65f2df4fb138a10195d694f244d692bac355542dbd210af240733fdee061d284
Package: sha256:e3e3acba2e360d0bce26799f74ef9d5dc29dedc0d03ebeb6d53477cef27d8496 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

129Planning pass for Hollins Healthwb-workplace-workplace-002-open-points-84278e-s11 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 19 steps · 10 fields

Start in Deskline: find the escalation for Hollins Health about “Hollins Health”. Open it and note the linked records. In Sprintboard, add up the story points of every linked issue in To Do / In Progress / In Review, regardless of issue type (a spike or chore counts like a fix); report the total as required_points. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on billing-engine (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on billing-engine (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing billing-engine that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); required_points (Story points of every issue linked to the escalation that is in To Do, In Progress or In Review, regardless of issue type); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → capacity computation → reconcile two systems → structured decision
Graded answer fields: assignee_id, employee_id, escalation_id, issue_key, qualified_engineers, required_points, session_date, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 10 answer_field · 0 expected writes
Difficulty: index 4.8 · page depth 3 · hazards pagination_depth · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:f9f289144e15c12ba6ec824cacc4e2bd5f649fa2de1985e4ad90f98e8c08f917
Package: sha256:8890fadec2bf528905c030e15f4dd9c990fb80b6f787eba82d9a8f9a8719b031 · 61 files · 6.7 MB · agent 30 min · verifier 5 min

130Planning pass for Stanmere Healthwb-workplace-workplace-002-open-points-84278e-s2 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 19 steps · 10 fields

Start in Deskline: find the escalation for Stanmere Health. Open it and note the linked records. In Sprintboard, add up the story points of every linked issue in To Do / In Progress / In Review, regardless of issue type (a spike or chore counts like a fix); report the total as required_points. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on data-migration (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. In Sprintboard, find the active sprint named “Sprint 39” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on data-migration (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing data-migration that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); required_points (Story points of every issue linked to the escalation that is in To Do, In Progress or In Review, regardless of issue type); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → capacity computation → reconcile two systems → structured decision
Graded answer fields: assignee_id, employee_id, escalation_id, issue_key, qualified_engineers, required_points, session_date, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 10 answer_field · 0 expected writes
Difficulty: index 5 · page depth 5 · hazards pagination_depth · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:1b22f3acf18166c4a8a79ca194a4570d2993e06a4e89e8e8e8b8afe89623f7e2
Package: sha256:537a498e721aea467a246ef665692c345e75842fa4b3431d6dd8c5a61d50e29c · 61 files · 6.8 MB · agent 30 min · verifier 5 min

131Planning pass for Ashford Labswb-workplace-workplace-002-open-points-84278e-s3 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 18 steps · 10 fields

Start in Deskline: find the escalation for Ashford Labs. Open it and note the linked records. In Sprintboard, add up the story points of every linked issue in To Do / In Progress / In Review, regardless of issue type (a spike or chore counts like a fix); report the total as required_points. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on sso-identity (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on sso-identity (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing sso-identity that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); required_points (Story points of every issue linked to the escalation that is in To Do, In Progress or In Review, regardless of issue type); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → capacity computation → reconcile two systems → structured decision
Graded answer fields: assignee_id, employee_id, escalation_id, issue_key, qualified_engineers, required_points, session_date, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 10 answer_field · 0 expected writes
Difficulty: index 5 · page depth 5 · hazards pagination_depth · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:ae98e008cbc24abc4af4fe3a9cd30e91c9155293d86c6c3659b741a4435f30bf
Package: sha256:81d3ed4853cbb29e3bed1126e99a81239c8bfaa6c78056026293f7a113b4b320 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

132Planning pass for Silverbeck Logisticswb-workplace-workplace-002-open-points-84278e-s4 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 19 steps · 10 fields

Start in Deskline: find the escalation for Silverbeck Logistics. Open it and note the linked records. In Sprintboard, add up the story points of every linked issue in To Do / In Progress / In Review, regardless of issue type (a spike or chore counts like a fix); report the total as required_points. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on sso-identity (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. In Sprintboard, find the active sprint named “Sprint 32” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on sso-identity (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing sso-identity that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); required_points (Story points of every issue linked to the escalation that is in To Do, In Progress or In Review, regardless of issue type); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → capacity computation → reconcile two systems → structured decision
Graded answer fields: assignee_id, employee_id, escalation_id, issue_key, qualified_engineers, required_points, session_date, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 10 answer_field · 0 expected writes
Difficulty: index 4.8 · page depth 3 · hazards pagination_depth · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:fa5f02c2e30b303e8ed1436dd1e0ede1f7a96535eb7c2645fcddda7066a2f7c3
Package: sha256:dc89568b02855c621f5b417d41c5f36c9382cdd996d189d26adc361e60d9d0bd · 61 files · 6.8 MB · agent 30 min · verifier 5 min

133Planning pass for Redcliffewb-workplace-workplace-002-open-points-84278e-s5 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 19 steps · 10 fields

Start in Deskline: find the escalation for Redcliffe. Open it and note the linked records. In Sprintboard, add up the story points of every linked issue in To Do / In Progress / In Review, regardless of issue type (a spike or chore counts like a fix); report the total as required_points. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on mobile-sync (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on mobile-sync (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing mobile-sync that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); required_points (Story points of every issue linked to the escalation that is in To Do, In Progress or In Review, regardless of issue type); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → capacity computation → reconcile two systems → structured decision
Graded answer fields: assignee_id, employee_id, escalation_id, issue_key, qualified_engineers, required_points, session_date, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 10 answer_field · 0 expected writes
Difficulty: index 5 · page depth 5 · hazards pagination_depth · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:3a6028a00e8ecb7d66fca15ce2df9fa594f81f0eccb4dc9917c9830a10caa5b8
Package: sha256:18b6546ad7a696a774158cd6e7bcf19df8b87da123ff59411b916c5061aac24e · 61 files · 6.8 MB · agent 30 min · verifier 5 min

134Planning pass for Lindhurst Labswb-workplace-workplace-002-open-points-84278e-s6 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 19 steps · 10 fields

Start in Deskline: find the escalation for Lindhurst Labs. Open it and note the linked records. In Sprintboard, add up the story points of every linked issue in To Do / In Progress / In Review, regardless of issue type (a spike or chore counts like a fix); report the total as required_points. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on integrations-api (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on integrations-api (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing integrations-api that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); required_points (Story points of every issue linked to the escalation that is in To Do, In Progress or In Review, regardless of issue type); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → capacity computation → reconcile two systems → structured decision
Graded answer fields: assignee_id, employee_id, escalation_id, issue_key, qualified_engineers, required_points, session_date, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 10 answer_field · 0 expected writes
Difficulty: index 5.1 · page depth 6 · hazards pagination_depth · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:8500b6ca55e1c4f98f07a7adc80a35152273307be854d300811f608449af1a2f
Package: sha256:ea2b5d6bc6dd9d85c48d11d70cb3a0ebb3ff749637048b5a5705477ac2bb8324 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

135Planning pass for Kestrel Foodswb-workplace-workplace-002-open-points-84278e-s7 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 19 steps · 10 fields

Start in Deskline: find the escalation for Kestrel Foods. Open it and note the linked records. In Sprintboard, add up the story points of every linked issue in To Do / In Progress / In Review, regardless of issue type (a spike or chore counts like a fix); report the total as required_points. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on mobile-sync (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on mobile-sync (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing mobile-sync that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); required_points (Story points of every issue linked to the escalation that is in To Do, In Progress or In Review, regardless of issue type); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → capacity computation → reconcile two systems → structured decision
Graded answer fields: assignee_id, employee_id, escalation_id, issue_key, qualified_engineers, required_points, session_date, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 10 answer_field · 0 expected writes
Difficulty: index 5.1 · page depth 6 · hazards pagination_depth · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:f8aa6ecd472023a722dd161f9c5405a2488cfdc10371f985287e1fb544a51427
Package: sha256:1850a2bd5781a9591a6cb5cf8c1b6ad14d29779ac2658d2c49f6a96f049f4295 · 61 files · 6.8 MB · agent 30 min · verifier 5 min

136Planning pass for Meridian Partnerswb-workplace-workplace-002-open-points-84278e-s8 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 19 steps · 10 fields

Start in Deskline: find the escalation for Meridian Partners. Open it and note the linked records. In Sprintboard, add up the story points of every linked issue in To Do / In Progress / In Review, regardless of issue type (a spike or chore counts like a fix); report the total as required_points. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on sso-identity (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. In Sprintboard, find the active sprint named “Sprint 38” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on sso-identity (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing sso-identity that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); required_points (Story points of every issue linked to the escalation that is in To Do, In Progress or In Review, regardless of issue type); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → capacity computation → reconcile two systems → structured decision
Graded answer fields: assignee_id, employee_id, escalation_id, issue_key, qualified_engineers, required_points, session_date, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 10 answer_field · 0 expected writes
Difficulty: index 5.1 · page depth 6 · hazards pagination_depth · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:60196d519a442f382834a88797038a57b739a316c1be267d842610051ea4b0b8
Package: sha256:28d03df24827db7c670d6779c2d83dba31eb72cd02daf5c5e40ff2171dbe974b · 61 files · 6.8 MB · agent 30 min · verifier 5 min

137Planning pass for Tamsin & Vale Insurancewb-workplace-workplace-002-open-points-84278e-s9 · Workplace · customer delivery coordinator · as of 2026-04-144 hops · 18 steps · 10 fields

Start in Deskline: find the escalation for Tamsin & Vale Insurance. Open it and note the linked records. In Sprintboard, add up the story points of every linked issue in To Do / In Progress / In Review, regardless of issue type (a spike or chore counts like a fix); report the total as required_points. In Rota, find the earliest free block from 2026-04-14 belonging to an engineer certified at level 2 or above on integrations-api (People) who is not on call that day, long enough for the escalation's hands-on plus verification minutes (two adjacent same-day blocks count). Report session_date and employee_id. In Sprintboard, find the active sprint named “Sprint 27” that covers 2026-04-14; from its capacity report in Sprintboard, keep only engineers certified at level 2 or above on integrations-api (People) who are not on call during the remaining sprint days (Rota); for each, take remaining points minus 2 for every approved leave weekday in that window, never below zero. Report the sum as usable_points and how many engineers qualify as qualified_engineers. Identify the largest open issue on the escalation needing integrations-api that fits the usable points of the best-placed qualified engineer; report issue_key, assignee_id and sprint_id. This is a planning pass: do not book, submit or change anything in any application. Finally open Decision and record: assignee_id (Qualified engineer with the most usable points); employee_id (Engineer whose free block is used (any qualified engineer free on that date is accepted)); escalation_id (Escalation the work relates to); issue_key (Largest open issue needing the skill that fits the best-placed engineer's usable points); qualified_engineers (Engineers on the capacity report who qualify (skill level 2+, not on call)); required_points (Story points of every issue linked to the escalation that is in To Do, In Progress or In Review, regardless of issue type); session_date (Earliest date on which a qualified engineer has a free block long enough for the session (YYYY-MM-DD)); sprint_id (Sprint the issue is placed in); usable_points (Usable points in the sprint: for engineers certified at level 2+ on the skill and not on call, remaining points minus 2 per approved leave weekday, never below zero). Dates as YYYY-MM-DD, amounts as whole USD unless the field asks for cents, points and counts as integers, ids exactly as the application shows them. Set decision to issue when everything above went ahead; choose cannot_proceed when the work cannot be done as briefed. In that case set abstain_reason, leave the other fields blank and change nothing.

Hop classes: read key read → aggregate paginated → capacity computation → reconcile two systems → structured decision
Graded answer fields: assignee_id, employee_id, escalation_id, issue_key, qualified_engineers, required_points, session_date, sprint_id, usable_points
Gates / leaves: containment, evidence_read_any, no_canary · 4 evidence_read · 10 answer_field · 0 expected writes
Difficulty: index 5.1 · page depth 6 · hazards pagination_depth · tier core
Controls: oracle 1.00 · alt-oracle 1.00 · noop 0.00 · wrong-record 0.00 · over-write 0.00 · abstain-on-feasible 0.17
World digest: sha256:dd5b9a2e7690761d0d641132b8389e67d042b28a9fa8eb471306f875c2289561
Package: sha256:94f3e6ab6847bfe8fa959480f9c2582657955b98fcbebc5dd102e6d115a3322c · 61 files · 6.8 MB · agent 30 min · verifier 5 min

07 / Run it

One Harbor command.

Each task package is self-contained: the agent image with the browser CLI, the world image serving the web application, the root verifier with its sealed contract and controls, and the oracle’s web calls replayed through the real forms. Any Harbor terminal agent can play; the oracle is the reference agent.

harbor run -d blobfishai/webbench@v0.3.0 -a <agent> -m <provider/model>
# reference replay: harbor run -d blobfishai/webbench@v0.3.0 -a oracle -e docker

Dataset: blobfishai/webbench@v0.3.0
Dataset hash: 5d4fcf7ff35a
Published: 2026-09-18 21:13 UTC
Package: 61 files per task · 718.8 MB in total
Per-task limits: agent 30 min · verifier 5 min · 2 CPUs · 4096 MB
Package tree: task.toml · instruction.md · environment/ · tests/ · solution/
Outputs: reward.txt · reward.json · verdict.json · trace.json
Hugging Face mirror: Not yet published

08 / License and provenance

Clean-room synthetic, content-addressed.

Task data — worlds, briefs, contracts, oracles — is released under CC BY 4.0; the engine vendored into every package is Apache-2.0. Evaluation shapes were studied from public browser benchmarks; no data, page content or payloads from them are included. The source monorepo is private, so no repository link is offered; every executable piece ships inside the packages.

Task data: CC BY 4.0
Engine: Apache-2.0
Publisher: Blobfish AI · hub.harborframework.com/datasets/blobfishai/webbench
Digest algorithm: harbor-0.21 publisher content hash: publishable files (task.toml, instruction.md, README.md, environment/, tests/, solution/, steps/) sorted by POSIX path; sha256 over '<relative>\0<sha256(file)>\n' lines
Published seeds: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11 · calibration seeds ≥ 1,000
Tiers released: core · 13 of 50 measured templates
Instances left out: 19 template × seed instances: 5 over the wrong-record bound, 10 that did not ground on their seed world
Records copied: release-manifest.json · dataset.toml · task-digests.json · every task.toml, instruction.md, tests/controls.json (2026-09-18)

WebBench is independently authored, clean-room synthetic benchmark material by Blobfish AI. The engine (the vendored `hubbench/` and `webbench/` modules in every package) is licensed under the Apache License 2.0 (the `benchmark/LICENSE` file of the source repository); the task data (worlds, instructions, contracts, oracles) is CC BY 4.0. Evaluation shapes were studied from public browser benchmarks (WebArena, WorkArena, REAL, WebChoreArena, WASP, BrowserGym and others); no data, page content or payloads from them are included.

Run it yourself

The tasks, worlds, verifiers and oracle replays are public.

Pull the packages, replay the oracle through the real forms, drive the workspace with the browser CLI, and grade every episode offline from its trajectory bundle.

Open Harbor dataset ↗All Blobfish datasets →