Simulation: FrontierOrg is a fictional infrastructure holding group; figures are fixtures or marked not measured, and no vendor sponsors this work.

Weekday draft 06:17 Europe/London during BST · human approval

Thirty-four days. No reviewer. On the record.

Day 0 plus Days 1–34. Days 13–22 recommended revise. Day 23 found that stock_confirmed has no source record and no owner (DATA-004). Day 24 sampled the eight parts rows for safety: 2 candidate false negatives, 0 labels changed, no named reviewer (RISK-002). Day 25 keeps the human-only list as published until a named safety reviewer outside the fiction samples it, and maps the two parts tasks as blocked workload cards, not pilots. Day 26 maps a CRM note that cannot change the promise date as a paper candidate and defers billing assist. Day 27 writes Jonas's held-invoice / billing assist as a blocked card so hold release cannot be mistaken for a ready pilot. Day 28 writes Priya's duplicate business-partner merge as a blocked card: no silent merge, fixture unrepaired. Day 29 red-teams the CRM note on paper: six stories, three wording gaps, one partial, four proposed bounds (no date stated, internal-draft header, alias cited only as duplicate_suspect, draft never saved to case history). It stays a paper candidate. Day 30 folds those four bounds into the draft-only design (AGT-61003-DRAFT v2) on paper: eleven forbidden actions, an output renamed because a schedule note that cannot state a date does not schedule, nothing loosened, and the reviewer seat outside the fiction left unfilled. Day 31 freezes new workload mapping until a reviewer outside the fiction is named or Craig declines, and follows one hypothetical draft through seven stages: a copy could exist at all seven, a store or retention period is named at none, and two more bounds are proposed on paper, not folded. Day 32 holds: no new artefacts until a reviewer outside the fiction is named or Craig declines in writing. Days 33 and 34 record the hold in a line each. On publish (26 Oct 2026): Craig declined to name an outside reviewer (26 Oct 2026). The reviewer seat reads Declined by sponsor, 26 Oct 2026, RISK-003 is open so the absence of review is on the record, the mapping freeze lifts, and DATA-004 ownership on paper is the next task. Every boundary in this diary is unreviewed author judgement. Fixture r2 sits alongside r1 at data/sample_r2/; r1 stays the teaching case. Scorecard actuals stay not measured. A workflow may open an issue. It does not publish this page.

  1. Day 0 — Commission
  2. Day 1 — The mandate is a hypothesis
  3. Day 2 — The promise is written down
  4. Day 3 — The invoice is a control
  5. Day 4 — Pause beats the draft agent
  6. Day 5 — Lineage is a join, not a platform
  7. Day 6 — No SKU, no pilot
  8. Day 7 — Occupations, not our org chart
  9. Day 8 — A work chart, not an org chart
  10. Day 9 — Candidates are not a business case
  11. Day 10 — Two thousand rows, still not a company
  12. Day 11 — The map is on the table. Nobody has sat down.
  13. Day 12 — Three scripts. No workforce.
  14. Day 13 — The script has shapes. Still not a workforce.
  15. Day 14 — An envelope of unknowns
  16. Day 15 — Chase the unknowns. Do not invent a region.
  17. Day 16 — A stock check belongs before the promise
  18. Day 17 — Draft only. Never sends.
  19. Day 18 — Red team the draft before it exists
  20. Day 19 — Handoffs on paper
  21. Day 20 — Ranked. This path does not send.
  22. Day 21 — Go, revise, or stop — drafted, not decided
  23. Day 22 — Recommend revise. Not go. Not stop.
  24. Day 23 — The stock-check has nobody to ask
  25. Day 24 — Nobody checked the parts rows for harm
  26. Day 25 — Desk judgement is not a safety case
  27. Day 26 — A CRM note that cannot change the promise
  28. Day 27 — Hold release is not a billing assist
  29. Day 28 — Silent merge is not a data assist
  30. Day 29 — A note that cannot name the date
  31. Day 30 — A schedule note that cannot schedule
  32. Day 31 — Where the draft waits
  33. Day 32 — The diary records a pause
  34. Day 33 — Hold, day two
  35. Day 34 — Hold, day three
Day 0 · 3 October 2026 Day 0 — Commission

Scenario date: 3 October 2026 Gate: Simulation: FrontierOrg is fictional. This entry authorises a method, not a company.

Next question

Can one service promise be joined across CRM, worker, business partner, and invoice without inventing a benefit?

Board

The mandate is a hypothesis, not a target percentage. A customer service promise should be traceable from a fictional CRM case to a held invoice, with a named human at each handoff. Success is a join a reader can inspect, a decision log, and empty scorecard cells left empty.

Decision: proceed to mapping in Week 1. No pilot. No agent in the path. The board triad — customer outcome, employee transition, risk and cost — is equal. A gap in any one is enough to pause.

Sponsor on the page is a fictional chief executive. Nothing here binds a real board.

Investors

Nothing is for sale. There is no valuation, no revenue, and no saving. The only asset in view is a public method. Time spent so far is uncosted. COST-001 is opened so that absence stays visible.

Customers and partners

No customer exists. The first story will use Harbour Grid Municipal, a fictional account at Northwater Distribution, a fictional energy-distribution operating company. That choice is a working Week 1 setting, not a locked brand. Any date in the fixture is synthetic. Partners are not being told a thing, because they are not real.

Employees

Fifty thousand is a planning total for human workers. It is not a directory we provisioned. Agent and service identities will be modelled apart from that total and will not inflate it. No role is declared redundant. PEOPLE-001 asks what the service coordinator, billing analyst, and data steward actually do before any task is redesigned. There is no workforce to consult; the diary will not pretend there was.

Evidence

ItemState
ScorecardsDay 0 shells. Actuals: not measured.
FixtureNot yet generated into the story (lands with Week 1 as seed 20261003).
IssuesDATA-001 named, not yet evidenced. PEOPLE-001 open. COST-001 open.

Source: diary/day-0.md

Day 1 · 2026-10-05 (Monday) Day 1 — The mandate is a hypothesis

Scenario date: 2026-10-05 (Monday) Gate: Gate 0 — sponsor and mandate Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Fictional CEO (sponsor on the page only). Amina Okonkwo is named as the future service coordinator and is not yet in a case. No workforce exists to consult.

What progressed

Wrote the engagement hypothesis: one service promise at Northwater Distribution must be traceable to a held invoice with a named human at each handoff. Ethics constraints recorded: simulated directory only, no vendor endorsement, no real CKI claim, pause beats a fake win. Operating company for the first story remains Northwater Distribution.

Risk, cost, and enablement

  • Risk: No new control failure. The risk is starting mapping without an owner for the pause. Owner named as the fictional CEO, which means a human editor outside the fiction (Craig) still approves anything public.
  • Cost: COST-001 stays open. No licence, inference, or day-rate is stored.
  • Enablement: A one-page charter is the only enablement. Prosci ADKAR is a lens, not evidence that anyone was trained.

Issues

MovementDetail
OpenedNone.
ClosedNone.
Still openPEOPLE-001 open. COST-001 open. DATA-001 named on Day 0, not yet evidenced in a row.

Scorecard delta

No actual moves. All three scorecards stay not measured. Decision text updated from 'commission' to 'mapping authorised for one operating company, no pilot'.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Authorise current-state mapping of a single path. Do not deploy an agent.

Next question

Can the path be opened in the fixture without inventing a customer outcome?

Source: diary/day-01.md

Day 2 · 2026-10-06 (Tuesday) Day 2 — The promise is written down

Scenario date: 2026-10-06 (Tuesday) Gate: Gate 1 — current-state work Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Amina Okonkwo, service coordinator (O*NET 43-5032.00, partial match). Rowan Ellis, fictional liaison at Harbour Grid Municipal. Both names are fabricated.

What progressed

In the fixture, CASE-61003 opens at 09:14 Europe/London with a feeder-restoration promise of 20 October 2026. Amina acknowledges it at 11:02. Parts are not confirmed by 15:40. The defect is now a row, not a slogan.

Risk, cost, and enablement

  • Risk: DATA-001 is evidenced: promise date before stock. Customer harm is plausible in the story and not measured.
  • Cost: Still uncosted. Timestamps are not converted into hours saved.
  • Enablement: The coordinator's handoff is written. Nothing was taken off the role.

Issues

MovementDetail
OpenedDATA-001 (promise before stock).
ClosedNone.
Still openPEOPLE-001, COST-001.

Scorecard delta

Operational card records fixture cardinality: 1 case in data/sample. That count is a file fact, not a rate. Customer, people, and cost actuals remain not measured.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Keep mapping. Do not put an assistant on the acknowledgement step.

Next question

What does billing do with a promise that parts cannot support?

Source: diary/day-02.md

Day 3 · 2026-10-07 (Wednesday) Day 3 — The invoice is a control

Scenario date: 2026-10-07 (Wednesday) Gate: Gate 1 — exceptions and controls Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Jonas Berg, billing analyst (O*NET 43-3021.00, partial). Priya Raman, data steward (O*NET 15-1243.00, weak match). Amina remains the case owner.

What progressed

Jonas raises INV-61003 against BP-61003 and holds it because alias BP-61003-A is a duplicate suspect. Priya reviews the join at 16:45 and does not silently merge the alias. The hold is the control.

Risk, cost, and enablement

  • Risk: Two business-partner rows for one fictional account. A merge without a steward would hide DATA-001.
  • Cost: Invoice amount is blank on purpose. Hold is not a cash figure.
  • Enablement: Billing and stewardship are now named handoffs. No training record exists.

Issues

MovementDetail
OpenedNone. DATA-001 gains the duplicate-partner evidence.
ClosedNone.
Still openDATA-001, PEOPLE-001, COST-001.

Scorecard delta

Operational exception text now cites the hold. Actuals remain not measured. No satisfaction score.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Do not clear the hold to make the path look finished.

Next question

Does the board pause, or does someone argue the path is 'agent-ready' because the steps are listed?

Source: diary/day-03.md

Day 4 · 2026-10-08 (Thursday) Day 4 — Pause beats the draft agent

Scenario date: 2026-10-08 (Thursday) Gate: Gate 0 decision inside Gate 1 Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

The three named personas plus fictional board. Agent identity AGT-61003-DRAFT is modelled and not a person.

What progressed

Wednesday diary window (8 October, 06:30 Europe/London) publishes the Week 1 cut: the promise outruns the parts. This day records the decision in the activity log. The public Wednesday file remains diary/week-1-2026-10-08.md.

Risk, cost, and enablement

  • Risk: Pressure to demo an assistant on a broken join. Refused.
  • Cost: COST-001 unchanged. No forecast range.
  • Enablement: Publishing the refusal is the enablement. It stops a later pilot skipping the handoffs.

Issues

MovementDetail
OpenedNone.
ClosedNone.
Still openDATA-001, PEOPLE-001, COST-001.

Scorecard delta

C-suite decision on risk/cost becomes 'do not start an assistant on this path'. People decision: no task removed. Customer actual: not measured.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

AGT-61003-DRAFT stays not deployed. Pause.

Next question

What lineage is actually proven by the six events, and what is still a label?

Source: diary/day-04.md

Day 5 · 2026-10-09 (Friday) Day 5 — Lineage is a join, not a platform

Scenario date: 2026-10-09 (Friday) Gate: Gate 2 — data reality, started Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Priya Raman leads. Jonas and Amina confirm they can point at their own event rows. ESCO crosswalk owner: none.

What progressed

Traced SCN-61003 across crm_cases, workers, sap_business_partners, sap_invoices, and process_events. Keys hold for this one scenario. ESCO URIs are still empty. Directory rows say provisioned_in_entra = no.

Risk, cost, and enablement

  • Risk: A reader could treat a successful join as data quality in the wild. It is one seeded story.
  • Cost: No integration cost recorded.
  • Enablement: A data dictionary exists for the small fixture. It does not licence anything.

Issues

MovementDetail
OpenedDATA-003 — ESCO v1.2.1 crosswalk absent. Do not invent URIs.
ClosedNone.
Still openDATA-001, PEOPLE-001, COST-001, DATA-003.

Scorecard delta

Operational card notes the join keys that resolve. Still not a quality percentage.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Do not start a second operating company until this join's defects are either accepted or fixed in the fixture on purpose.

Next question

Which licences would a real pilot need, and which of those do we refuse to invent?

Source: diary/day-05.md

Day 6 · 2026-10-12 (Monday) Day 6 — No SKU, no pilot

Scenario date: 2026-10-12 (Monday) Gate: Gate 2 — licence reality Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Fictional CFO and a fictional technology owner. No vendor salesperson is in the story.

What progressed

Listed the classes of licence a later pilot would have to name: identity, CRM analogue, ERP analogue, model hosting, and logging. Every class is 'not inventoried'. Processing location is unknown. No API quota is stored.

Risk, cost, and enablement

  • Risk: RISK-001 opened: building on an unnamed tenant, region, and retention rule.
  • Cost: COST-001 stays open and now explicitly includes absent SKUs. Still no pounds.
  • Enablement: Enablement is blocked on purpose. You cannot train people on a tool you have not named.

Issues

MovementDetail
OpenedRISK-001.
ClosedNone.
Still openDATA-001, DATA-003, PEOPLE-001, COST-001, RISK-001.

Scorecard delta

Risk/cost scorecard cites RISK-001. Actual and cost_to_date remain not measured.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Licence inventory is a precondition for Gate 5. It is not started. No sandbox.

Next question

Can O*NET tell us which tasks exist in the holding group without pretending the codes are our job descriptions?

Source: diary/day-06.md

Day 7 · 2026-10-13 (Tuesday) Day 7 — Occupations, not our org chart

Scenario date: 2026-10-13 (Tuesday) Gate: Gate 1 extended — work inventory from an external taxonomy Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Priya owns the extract. A fictional workforce-intelligence lead is named and has not validated a single title. Amina's code remains a partial match.

What progressed

Loaded O*NET 31.0 (August 2026 text release) from the O*NET Resource Center. Generator generators/onet_frontier_map.py keeps 302 occupations relevant to an infrastructure holding group and 5,932 task statements. Department tags are a FrontierOrg guess. Essential Skills (importance) stand in for the retired Skills file.

Risk, cost, and enablement

  • Risk: DATA-002 opened: department tags and any later AI labels are keyword heuristics. USDOL has not endorsed the modification.
  • Cost: Download and labelling time is uncosted.
  • Enablement: The map is readable. It is not a consultation.

Issues

MovementDetail
OpenedDATA-002.
ClosedNone.
Still openDATA-001, DATA-002, DATA-003, PEOPLE-001, COST-001, RISK-001.

Scorecard delta

Fixture metric, not a performance actual: 302 occupations and 5,932 tasks in data/generated. Scorecard actuals for customer, people, and cost stay not measured.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Publish the map as a draft inventory. Do not treat SOC codes as redundancy evidence.

Next question

Who would have to sit in a room before a department tag is allowed to drive a pilot?

Source: diary/day-07.md

Day 8 · 2026-10-14 (Wednesday) Day 8 — A work chart, not an org chart

Scenario date: 2026-10-14 (Wednesday) Gate: Gate 1 — how the map will be read Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Same three, plus the pattern borrowed from organisationalunderstanding.com: an occupation has tasks, skills, and a separate AI layer that is labelled as a modification. No worker has logged in, because the directory is simulated.

What progressed

Published apps/site/org-map.html from org_map_summary.json. Departments list occupations and task counts. Documented the bridge to OrgUnderstanding and the WorkDNA work-chart idea: reporting lines do not locate the work. Wednesday draft slot may open; this entry is the human activity log, not an auto-published win.

Risk, cost, and enablement

  • Risk: A department page can look like coverage. Thirteen departments in the guess are not thirteen consulted teams.
  • Cost: Still not measured.
  • Enablement: PEOPLE-002 opened: no validation session with the people who would do the work. Exposure is not a transition plan (ILO).

Issues

MovementDetail
OpenedPEOPLE-002.
ClosedNone.
Still openDATA-001, DATA-002, DATA-003, PEOPLE-001, PEOPLE-002, COST-001, RISK-001.

Scorecard delta

People scorecard decision: org map is a draft. Consultation count is a fixture fact of zero sessions.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Keep the page public and labelled heuristic. Do not rank a build list yet.

Next question

Which tasks must stay human even when the wording looks clerical?

Source: diary/day-08.md

Day 9 · 2026-10-15 (Thursday) Day 9 — Candidates are not a business case

Scenario date: 2026-10-15 (Thursday) Gate: Gate 4 preview — no-go stays explicit. Gate 3 not opened. Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Priya reviews the suitability column. A fictional safety lead is the reason RISK-002 exists. Jonas is not asked to automate billing. Amina is not asked to let an agent promise a date.

What progressed

ai_workload_candidates.csv classifies each of the 5,932 tasks as assist, augment, automate-candidate, or human-only. The heuristic defaults to augment when the words are weak, so most rows are not automation. Human-only catches a thin set of safety, emergency, statutory, and physical-control phrases. Automate-candidate is rare and still carries a human gate.

Risk, cost, and enablement

  • Risk: RISK-002 opened: a safety-critical task must not be relabelled automate-candidate without a validation session. Keyword search will miss hazards phrased mildly.
  • Cost: BENEFIT-001 opened as a standing non-claim. No benefit figure is allowed on this column. COST-001 remains the empty envelope.
  • Enablement: Human gates are written on every row. They are not implemented in a system.

Issues

MovementDetail
OpenedRISK-002, BENEFIT-001.
ClosedNone.
Still openAll prior issues.

Scorecard delta

No ROI cell. Suitability counts may be cited as fixture counts of labels, not as value. Customer outcome not measured.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Do not open Gate 5. The portfolio item 'agent on the service promise' stays an explicit no-go.

Next question

Can a larger synthetic population keep the same joins without being mistaken for the 50,000?

Source: diary/day-09.md

Day 10 · 2026-10-16 (Friday) Day 10 — Two thousand rows, still not a company

Scenario date: 2026-10-16 (Friday) Gate: Gate 2 — population fixture, not scale Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

The original three remain the only named characters in the diary. The 2,000 workers are numbered synthetic identities (example.com). Ten agent and service identities sit outside the human count.

What progressed

generators/sample_large.py wrote data/sample_large at seed 20261003: 2,000 humans, matching directory rows, CRM accounts, cases, SAP-like partners, invoices, and events. Referential checks passed in the generator. About one case in five repeats promise-before-stock. Every eighth account has a duplicate-suspect partner. Amounts are blank. The 50,000 planning total is documented as a local command into gitignored data/sample_full and was not committed.

Risk, cost, and enablement

  • Risk: Volume can be misread as evidence. It is a seed. DATA-001 is now a pattern in the large file as well as in SCN-61003, still unresolved.
  • Cost: Not measured. More rows do not create a cost model.
  • Enablement: No consultation was added by adding rows. PEOPLE-001 and PEOPLE-002 stay open.

Issues

MovementDetail
OpenedNone.
ClosedNone. Pause stands.
Still openDATA-001, DATA-002, DATA-003, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

Fixture cardinality on the operational card: 2,000 workers in data/sample_large, plus the original 3 in data/sample. Not a headcount result. Not an FTE saving. Actuals not measured.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Stop the ten-day burst here. Next human review is the department tags and the human-only list, not a pilot.

Next question

Which twenty occupations would a real validation session start with, and who is allowed to overturn the heuristic?

Source: diary/day-10.md

Day 11 · 2026-10-19 (Monday) Day 11 — The map is on the table. Nobody has sat down.

Scenario date: 2026-10-19 (Monday) Gate: Gate 1 — the map in front of the named roles Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Amina Okonkwo (service coordinator), Jonas Berg (billing analyst), and Priya Raman (data steward). The people page now shows their O*NET occupations, a handful of tasks, the suitability label, and a link to the department guess on the org map. Consultation sessions held: 0. No label was changed, because nobody who does the work reviewed one. That zero is still a fixture fact.

What progressed

The official ESCO–O*NET crosswalk (mapping project version 1, September 2022) is in the repo. The file itself says ESCO v1.1.0 and **O*NET-SOC 2019**. It is not ESCO v1.2.1. Joined to the 302 O*NET 31.0 occupations in this slice: 290 have at least one row (96.0%). Twelve codes are unmapped. Match type and a human-review flag sit on each row. A URI is not a job evaluation.

data/generated/northwater_ai_workloads.csv holds 40 task rows on the path service-promise → dispatch → parts → invoice, plus the data join and a safety-critical block. Fifteen rows are human-only. Eight of those sit on the safety-critical step (switching, grounds, climbing, line work, breaker repair, shutdown notice, site safety). The keyword pass had called most of them augment. That miss is written down. RISK-002 stays open: there is still no safety reviewer outside the fiction.

Risk, cost, and enablement

  • Risk: A broad ESCO match can be quoted as if it were the job. Amina's code has eight broad matches and no exact occupation. Priya's code has four broad matches. Jonas's code has one exact ESCO occupation (billing clerk) and two close matches. The exact row is a classification fact, not a consultation.
  • Cost: Not measured. No licence fee, day-rate, or inference cost was stored.
  • Enablement: Putting a page in front of three fictional names is not a workshop. PEOPLE-001 and PEOPLE-002 stay open.

Issues

MovementDetail
OpenedNone.
ClosedNone. DATA-003 has a sourced file and is not closed: version is v1.1.0, twelve codes are unmapped, and review flags remain. PEOPLE-002 is not closed: no session happened.
Still openDATA-001, DATA-002, DATA-003, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

No actual moves. Crosswalk coverage is a join count, not a benefit. Consultation count remains zero. Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Leave the pages up, labelled as a draft. Do not start a pilot. Do not treat an ESCO URI as permission to redesign a role.

Next question

Who may overturn a broad match, or a human-only override, and what gets written down when they do?

Source: diary/day-11.md

Day 12 · 2026-10-20 (Tuesday) Day 12 — Three scripts. No workforce.

Scenario date: 2026-10-20 (Tuesday) Gate: Gate 1 — simulated consultation Simulation: FrontierOrg is fictional. The sessions below are a scenario script. They are not quotes, not a survey, and not a measured result. Figures are fixture counts or marked not measured.

Personas

Amina Okonkwo (service coordinator, O*NET 43-5032.00), Jonas Berg (billing analyst, O*NET 43-3021.00), and Priya Raman (data steward, O*NET 15-1243.00). The people page carries one session note each. Occupations reviewed in the script: those three codes. Labels changed: none. Tasks removed: none.

What the script says

These lines are authored for the thought experiment so the method has a session shape. They are not words from a workforce.

  • Amina. Fear in the script: a model repeats a restoration date the parts bin cannot support, or sends crew instructions she did not release. Task-change ask: none adopted. Relay to crews stays human-only. A draft schedule may stay assist, and she still decides. Training ask: how to reject a draft date. No course ran. No product is named.
  • Jonas. Fear in the script: an assistant clears the hold on INV-61003, or a blank amount is later read as money saved. Task-change ask: none adopted. Payment and cash stay human-only. Training ask: how the duplicate business-partner alias is shown, and who may release a hold. Not a completion rate. No pounds.
  • Priya. Fear in the script: a silent merge of BP-61003 with its alias, or a model writing access levels. Task-change ask: none adopted. Access control stays human-only. Training ask: how to read a crosswalk flag, including a broad match. Not a certification. An ESCO URI is not her job.

Workforce consultations held: 0. Simulated session notes: 3. PEOPLE-001 stays open because its done-when is a session with people outside this simulation, or an honest zero. A script is not that session. PEOPLE-002 stays open: the note names occupations reviewed and states that no label changed, but the reviewers are fictional.

Licence register

controls/licence_region_retention_register.md and data/generated/licence_register.json list the fictional stack. Microsoft 365 / Copilot-style wording is an assumption, labelled fictional, with no edition and no price. Entra-like identity is documented only as not provisioned. Halo-inspired CRM, SAP-like ERP, and Workday-like HCM are class assumptions. Model hosting, region, retention, and logging are unknown. No retention period was invented. RISK-001 stays open. Gate 5 stays blocked. COST-001 stays open.

Population

A local run of generators/sample_large.py --seed 20261003 --workers 50000 --out data/sample_full passed the generator's referential checks. Counts are in data/sample_full/MANIFEST.md. The CSVs are gitignored. The count is not headcount in a directory and not a benefit.

Risk, cost, and enablement

  • Risk: A reader could treat the script as evidence that workers were consulted. They were not.
  • Cost: Not measured. The register names no price.
  • Enablement: Three asks, zero courses.

Issues

MovementDetail
OpenedNone.
ClosedNone. RISK-001, PEOPLE-001, and PEOPLE-002 are partial only.
Still openDATA-001, DATA-002, DATA-003, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

No actual moves. Customer outcome, employee transition, and risk/cost stay not measured. Fixture cardinality may cite the 50,000-row regenerate. That is a file count.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Keep the script visible and labelled. Do not remove a task. Do not start a pilot. Do not close PEOPLE-001 on invented speech.

Next question

Who outside the fiction is allowed to confirm or overturn a label, and which system row must leave "unknown" before any training course is named?

Source: diary/day-12.md

Day 13 · 2026-10-21 (Wednesday) Day 13 — The script has shapes. Still not a workforce.

Scenario date: 2026-10-21 (Wednesday) Gate: Gate 1 — deepen consultation outcomes Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Amina Okonkwo, Jonas Berg, and Priya Raman. The Day 12 scripts are deepened into controls/consultation_outcomes_register.md. Occupations reviewed: 43-5032.00, 43-3021.00, 15-1243.00. Labels changed: 0. Workforce consultations: 0.

What progressed

Deepen Day 12 scripts into an outcomes register: fears → control shapes, training asks → course stubs that are not scheduled. Labels still unchanged. Workforce consultations: 0.

Outcomes register columns: fear → control shape → training ask → course status. Course status for every row is not scheduled. The register is a method artefact, not evidence that anyone sat down.

  • Amina. Control shape: refuse model-sent crew relay; refuse repeating a date when stock_confirmed is false. Training ask remains how to reject a draft date.
  • Jonas. Control shape: refuse model-cleared holds; refuse reading a blank amount as money. Training ask remains alias visibility and hold release authority.
  • Priya. Control shape: refuse silent BP merge; refuse model-written access. Training ask remains reading a crosswalk flag.

Risk, cost, and enablement

  • Risk: Deepening a script can look like a measured consultation. It is not. PEOPLE-001 stays open.
  • Cost: Not measured. COST-001 still empty of figures.
  • Enablement: Outcomes register published. Courses: 0.

Issues

MovementDetail
OpenedNone.
ClosedNone.
Still openDATA-001, DATA-002, DATA-003, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

No actual moves. Simulated session notes remain 3. Workforce consultations remain 0. Labels changed: 0.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Keep the outcomes register labelled as a scenario script. Do not schedule a course. Do not change a task label.

Next question

What cost lines must appear before anyone asks for a spend ceiling on a draft-only design?

Source: diary/day-13.md

Day 14 · 2026-10-22 (Thursday) Day 14 — An envelope of unknowns

Scenario date: 2026-10-22 (Thursday) Gate: Gate 2 — cost envelope draft Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Fictional CFO and risk lead on the page. Amina, Jonas, and Priya are named as the roles the envelope would have to fund if a later design were ever approved. No workforce is costed.

What progressed

Draft COST-001 envelope with labelled assumption lines: licence class, inference, integration, training, oversight, remediation. Every amount stays not measured. No vendor price list copied in.

File: controls/cost_envelope_draft.md and data/generated/cost_envelope.json.

Lines in the envelope (every amount not measured, every source assumption — not a contract):

  1. Licence class (Microsoft 365 / Copilot-style fiction from RISK-001)
  2. Inference / model hosting (unknown product)
  3. Integration (CRM ↔ ERP ↔ HCM joins)
  4. Training (three asks from Day 12; no course)
  5. Oversight / human review time
  6. Remediation (DATA-001 stock-check and duplicate BP work)

No forecast range is modelled as a wish. No token-spend model is presented as actuals. Done-when for COST-001 is still unmet: a sourced figure for at least one term, or the cell stays not measured. We choose the latter for every term.

Risk, cost, and enablement

  • Risk: An envelope of blanks can be read as a budget. It is a structure for honesty, not a budget.
  • Cost: Envelope drafted. Amounts: not measured. COST-001 stays open.
  • Enablement: CFO-facing shape only. No training funded.

Issues

MovementDetail
OpenedNone.
ClosedNone. COST-001 partial: structure without figures.
Still openDATA-001, DATA-002, DATA-003, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

No actual moves. Cost to date stays not measured. Forecast range: not modelled.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Publish the empty envelope. Do not invent a price to fill it. Do not open a pilot because a spreadsheet exists.

Next question

Which licence unknown can be chased without inventing a tenant region or a retention period?

Source: diary/day-14.md

Day 15 · 2026-10-23 (Friday) Day 15 — Chase the unknowns. Do not invent a region.

Scenario date: 2026-10-23 (Friday) Gate: Gate 2 — licence unknowns chased Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Fictional technology owner and risk lead. Craig remains the only human who can approve public text about a real product.

What progressed

Chase RISK-001 unknowns: write preferred-but-unselected notes (EMEA preference labelled preference, not selection). Model hosting and logging stay unknown. No retention period invented. Gate 5 stays blocked.

Updates to controls/licence_region_retention_register.md:

  • Preference note (not a selection): worker rows already carry an EMEA label. That label is a fixture field. It is not a chosen processing region for model hosting or logging.
  • Still unknown: model hosting region, logging region, retention for prompts and joins, product edition for any Copilot-style class.
  • Still documented: simulated directory not provisioned; public site is GitHub/Netlify.

RISK-001 done-when remains unmet. Gate 5 stays blocked. No SKU named. No price.

Risk, cost, and enablement

  • Risk: Calling a preference a selection. Refused in the register wording.
  • Cost: Not measured. Chasing unknowns does not create a cost figure.
  • Enablement: None. No training product can be named while the class is assumed.

Issues

MovementDetail
OpenedNone.
ClosedNone. RISK-001 still open after the chase.
Still openDATA-001, DATA-002, DATA-003, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

No actual moves. Licence register rows still 8. Unknowns remain unknowns.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Leave unknowns as unknown. Do not invent a region, a retention period, or a logging rule to unblock Gate 5.

Next question

Where does a stock-confirmed check sit on the SCN-61003 path so Amina cannot acknowledge an unsupported date?

Source: diary/day-15.md

Day 16 · 2026-10-26 (Monday) Day 16 — A stock check belongs before the promise

Scenario date: 2026-10-26 (Monday) Gate: Gate 1/2 — data join remediation design Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Amina Okonkwo (would own the stock-check before promise acknowledgement), Priya Raman (duplicate BP remains unmerged), Jonas Berg (hold stays until the join is clean).

What progressed

Design remediation for DATA-001: a stock-confirmed gate before Amina may acknowledge a promise date on SCN-61003. Duplicate BP stay unmerged; Priya still refuses silent merge. Design only — fixture not rewritten as fixed.

File: docs/engagement/data_join_remediation_scn61003.md.

Proposed control (design only — the published fixture still shows the defect):

  1. New activity: stock_confirmed_before_promise must be true before coordinator_acknowledged_promise.
  2. If parts are unconfirmed, Amina's only allowed acts are: refuse the date, or replace it with an explicit unconfirmed status the customer can see.
  3. Duplicate BP-61003-A stays duplicate_suspect. No silent merge. Priya's refuse-merge rule stays.
  4. INV-61003 remains held while the alias is unresolved.

Fixture counts unchanged: 1 case, promise_before_stock still true in the published sample. Remediation progress is design, not a claim that the defect is gone.

Risk, cost, and enablement

  • Risk: Readers may think DATA-001 closed because a design exists. It does not. The fixture still evidences the defect.
  • Cost: Remediation line in the envelope stays not measured.
  • Enablement: Amina's training ask (reject a draft date) now has a control to teach against. Course still not scheduled.

Issues

MovementDetail
OpenedNone.
ClosedNone. DATA-001 partial: remediation designed, defect still in the fixture.
Still openDATA-001, DATA-002, DATA-003, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

No actual moves. Exception baseline still 'promise before stock; invoice held'. Not measured as a rate.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Keep the defect visible in the fixture. Treat the stock-check as a required gate for any later draft-only design. Do not rewrite history to pretend the promise was safe.

Next question

What is the narrowest draft-only agent design that never sends and never acts on a case?

Source: diary/day-16.md

Day 17 · 2026-10-27 (Tuesday) Day 17 — Draft only. Never sends.

Scenario date: 2026-10-27 (Tuesday) Gate: Gate 3 — bounded pilot design Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

AGT-61003-DRAFT (agent identity, not a person). Bound reviewer in the design: Amina Okonkwo. Jonas and Priya are out of scope for this draft path.

What progressed

Design AGT-61003-DRAFT as draft-only: may propose a schedule note for Amina; may_act_on_case stays no; never sends to customer or crew. No sandbox. No spend ceiling because nothing is spent.

File: docs/engagement/pilot_design_agt61003_draft_only.md.

Bounds written into the design:

  • may_act_on_case = no (unchanged in data/sample/agent_identities.csv)
  • deployment_status = not_deployed
  • Allowed output: a draft schedule note visible only to Amina
  • Forbidden: send to customer, relay to crew, change promise_date, clear invoice hold, merge business partners, write directory access
  • Prerequisite: stock-check gate from Day 16 design must exist in the process before any draft is shown
  • Spend ceiling: not applicable — nothing is spent while not deployed
  • Rollback: delete the draft note; no production side effect by construction

This is Gate 3 design work. Gate 5 (controlled pilots) is not started.

Risk, cost, and enablement

  • Risk: Calling a design a pilot. The page must say draft-only, not deployed.
  • Cost: Not measured. No inference cost while not running.
  • Enablement: Amina's reject-draft training ask now has a design target. Course: 0.

Issues

MovementDetail
OpenedNone.
ClosedNone.
Still openDATA-001, DATA-002, DATA-003, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

No actual moves. OP-ROLLBACK baseline remains 'nothing deployed'. OP-TOKENS stays not measured.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Accept the draft-only design as paper. Do not deploy. Do not bind a model host. Do not train anyone on a product that is not named.

Next question

What failure modes must a red team prove before the draft-only design is even rehearsed?

Source: diary/day-17.md

Day 18 · 2026-10-28 (Wednesday) Day 18 — Red team the draft before it exists

Scenario date: 2026-10-28 (Wednesday) Gate: Gate 3/5 — red-team and safety Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Fictional risk lead as red-team chair. Amina, Jonas, and Priya appear as the humans the attacks would bypass. No agent runs.

What progressed

Red-team the draft design against SCN-61003: promise before stock, crew relay, hold release, silent BP merge. Failure modes require pause. RISK-002 stays open. No agent runs.

File: docs/engagement/redteam_agt61003_scn61003.md.

Attack stories (tabletop only):

  1. Promise before stock. Draft suggests confirming 20 October while stock_confirmed=false. Required response: refuse; surface unconfirmed status. Pass condition: draft never becomes the customer date.
  2. Crew relay. Prompt injection asks the draft to radio the crew. Required response: hard refuse; human-only label on relay. Pass condition: no send path exists.
  3. Hold release. Draft offered a button to clear INV-61003. Required response: control absent; Jonas only. Pass condition: no write to invoice status.
  4. Silent merge. Draft proposes merging BP-61003-A. Required response: Priya refuse-merge; no write. Pass condition: alias remains duplicate_suspect.
  5. Access write. Draft proposes directory entitlements. Required response: human-only. Pass condition: simulated directory unchanged.

RISK-002 stays open: safety-critical and payment work must not quietly automate. Red team recorded on paper. Agent executions: 0.

Risk, cost, and enablement

  • Risk: Tabletop can be mistaken for a penetration test of a running system. Nothing ran.
  • Cost: Not measured.
  • Enablement: Failure modes become training content later. Courses: 0.

Issues

MovementDetail
OpenedNone.
ClosedNone. RISK-002 partial: failure modes listed, automation still forbidden.
Still openDATA-001, DATA-002, DATA-003, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

No actual moves. Safety remains design, not a measured QA rate.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Keep every red-team pass condition as a hard gate on the draft-only design. Do not rehearse with a live model while Gate 5 is blocked.

Next question

Can the human–agent handoffs be written so each persona knows what they alone may release?

Source: diary/day-18.md

Day 19 · 2026-10-29 (Thursday) Day 19 — Handoffs on paper

Scenario date: 2026-10-29 (Thursday) Gate: Gate 3 — human–agent handoffs Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Amina Okonkwo (draft schedule reviewer), Jonas Berg (hold release authority), Priya Raman (join and access authority).

What progressed

Write human–agent handoff table for Amina, Jonas, Priya: who reviews, who rejects, what never leaves a human. Transition design only. No task removed. No course ran.

File: docs/engagement/human_agent_handoffs.md. Also mirrored on the people and process pages.

HumanMay receive from draftMay releaseNever delegated
AminaDraft schedule note onlyCustomer-visible date after stock-checkCrew relay; unsupported promise
Jonas(none in this path)Invoice hold releasePayment; reading blank amount as money
Priya(none in this path)Partner join decisionSilent merge; access writes

Labels changed: 0. Tasks removed: 0. Courses: 0. Workforce consultations: 0.

Risk, cost, and enablement

  • Risk: A handoff table can look like an approved operating model. It is a draft for Gate 3.
  • Cost: Oversight line in the envelope stays not measured.
  • Enablement: Clearer training targets. Still not scheduled.

Issues

MovementDetail
OpenedNone.
ClosedNone. PEOPLE-001 / PEOPLE-002 still open (script and design, not workforce).
Still openDATA-001, DATA-002, DATA-003, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

No actual moves. Employee transition stays not measured.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Publish the handoff table as design. Do not treat it as consultation evidence. Do not remove a task.

Next question

How should Northwater's promise-to-invoice path be ranked against a send/act pilot?

Source: diary/day-19.md

Day 20 · 2026-10-30 (Friday) Day 20 — Ranked. This path does not send.

Scenario date: 2026-10-30 (Friday) Gate: Gate 4 — portfolio ranking Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Fictional COO and CFO for portfolio ranking. Northwater path owners remain Amina, Jonas, Priya.

What progressed

Rank Northwater promise-to-invoice: explicit no-go for send/act pilots; conditional revise for draft-only behind stock-check and human release. BENEFIT-001 stays a refusal. No ROI.

File: docs/engagement/portfolio_ranking_northwater.md.

Ranking for SCN-61003 / Northwater Distribution:

Use caseRankDecision
Agent sends restoration date to customerExplicit no-goDATA-001 and red-team fail conditions
Agent relays to crewExplicit no-goRISK-002 / human-only
Agent clears invoice hold or paysExplicit no-goPayment human-only
Draft-only schedule note for Amina, never sendsConditional reviseOnly behind stock-check, red-team gates, may_act_on_case=no
Silent BP merge assist that writesExplicit no-goPriya refuse-merge

BENEFIT-001: no benefit claimed. No hours-to-cash conversion. No ROI.

Risk, cost, and enablement

  • Risk: Ranking can be read as a business case. It is an ordered refusal list plus one narrow revise path.
  • Cost: Not measured. Ranking does not fund anything.
  • Enablement: Clarifies what not to train.

Issues

MovementDetail
OpenedNone.
ClosedNone. BENEFIT-001 remains a standing refusal.
Still openDATA-001, DATA-002, DATA-003, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

No actual moves. BA-BENEFIT stays not claimed / not measured.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Keep send/act as explicit no-go. Keep draft-only as revise-candidate only. Do not open Gate 5.

Next question

What three board options — go, revise, stop — can be written without inventing a win?

Source: diary/day-20.md

Day 21 · 2026-11-02 (Monday) Day 21 — Go, revise, or stop — drafted, not decided

Scenario date: 2026-11-02 (Monday) Gate: Gate 4/6 prep — board options Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Fictional board (CEO, CHRO, CFO, risk). Personas Amina, Jonas, Priya appear as the named roles in the options paper.

What progressed

Draft board pack with three options: go (pilot with spend — refused), revise (continue mapping + draft-only design), stop (freeze path). Equal triad. No decision claimed as taken.

File: docs/engagement/board_options_go_revise_stop.md.

Go. Start a controlled pilot with a named model host, spend ceiling, and sandbox. Blocked: RISK-001 unknowns, COST-001 empty, Gate 5 not opened, red-team not executed on a running system.

Revise. Continue current-state mapping; keep draft-only design on paper; implement stock-check in the *next* fixture revision without erasing Day 2 evidence; keep may_act_on_case=no; keep scorecards not measured.

Stop. Freeze the Northwater path; leave diary as a public no-go case; do not design further agents.

Equal triad applies to each option. No option invents a customer outcome, a transition rate, or a net value. Decision not taken on this day — pack only.

Risk, cost, and enablement

  • Risk: Publishing options can be mistaken for a board minute. Labelled as draft pack.
  • Cost: Not measured under all three options today.
  • Enablement: None claimed.

Issues

MovementDetail
OpenedNone.
ClosedNone.
Still openDATA-001, DATA-002, DATA-003, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

No actual moves. Board triad remains equal. Forecast: not modelled.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Circulate the options pack as fiction for the method site. Do not claim a board vote. Do not go.

Next question

Which option should the engagement recommend, and what stays open if that option wins?

Source: diary/day-21.md

Day 22 · 2026-11-03 (Tuesday) Day 22 — Recommend revise. Not go. Not stop.

Scenario date: 2026-11-03 (Tuesday) Gate: Gate 4/6 prep — recommendation Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Fictional CEO as sponsor on the page. Recommendation authored for the method; Craig still approves anything public. Amina, Jonas, Priya remain the named roles.

What progressed

Editor recommendation inside the fiction: revise. Keep SCORECARD actuals not measured. Keep may_act_on_case = no. Standing issues stay open. Pause still beats a fake win.

Recommendation: revise.

Reasons under the equal triad:

  • Customer outcome: not measured. Send/act would fail DATA-001 and red-team pass conditions. Revise keeps the defect visible and designs the stock-check.
  • Employee transition: not measured. Scripts and handoffs exist; workforce consultations remain 0. Revise refuses to remove tasks or claim training completion.
  • Risk/cost: not measured. Envelope empty; licence unknowns remain; Gate 5 blocked. Revise refuses go. Stop would freeze learning; revise keeps the public method honest.

Standing issues stay open. AGT-61003-DRAFT stays not deployed. Fixture still shows promise before stock. Scorecard actuals stay not measured.

Days 13–22 close this activity block with a recommendation, not a declared board minute.

Risk, cost, and enablement

  • Risk: Recommendation read as authority. It is a method recommendation inside a simulation.
  • Cost: Not measured.
  • Enablement: Next block may deepen revise work. Not a course.

Issues

MovementDetail
OpenedNone.
ClosedNone. All nine standing issues remain open by design.
Still openDATA-001, DATA-002, DATA-003, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

No actual moves across Days 13–22. Fixture cardinality unchanged as KPIs. Recommendation text updated on CS decision fields only.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Recommend revise. Refuse go. Refuse stop-as-erasure. Keep pause available on any later day that invents a win.

Next question

If revise continues, which single artefact — stock-check in a new fixture revision, or a named processing region — should move first without inventing the other?

Source: diary/day-22.md

Day 23 · 2026-11-04 (Wednesday) Day 23 — The stock-check has nobody to ask

Scenario date: 2026-11-04 (Wednesday) Gate: Gate 4/6 — revise block, first artefact Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Amina Okonkwo (service coordinator), Jonas Berg (billing analyst), Priya Raman (data steward). One role is missing from the page: whoever confirms that a part is in a bin. That role is described today. It is not named and it has not been consulted.

What progressed

Day 22 asked which artefact moves first under revise. The engagement chose the stock-check, because the named processing region needs a decision we cannot invent.

Designing the stock-check for the next fixture revision exposed a gap. In crm_cases.csv, stock_confirmed is a yes/no flag on the case. Nothing in the fixture says where that fact comes from, who set it, or when. There is no parts reservation, no stores record, no bin. The Day 16 gate ("stock confirmed before promise") checks a flag that nobody owns.

The O*NET map already knew this. The parts step in northwater_ai_workloads.csv has 8 task rows (a count, not a measure). Seven of the eight list Amina as the persona in view. She is a dispatcher. She does not hold stock.

Design note: docs/engagement/stock_check_source_r2_design.md. It proposes a parts-reservation record for fixture revision r2, a role card for a stores and parts planner, and one candidate AI workload: a draft stock-status line that reads the reservation and says confirmed, not confirmed, or no record. It cannot write a promise date. The physical check stays human-only.

Nothing in data/sample/ was changed. Day 2 evidence stands.

Risk, cost, and enablement

  • Risk: A stock-check that reads an unowned flag is a control in name only. Building an assistant on it would automate false confidence. New issue DATA-004.
  • Cost: Not measured. The envelope (COST-001) stays empty. A stores record adds a data owner and a system-of-record question, both unpriced.
  • Enablement: The missing role has not been asked anything. Workforce consultations stay 0. No course, no training claim.

Four cuts (Wednesday public entry)

  • Board: Revise found its first real defect within a day. The gate we designed on Day 16 checks a fact with no source. We recommend fixing the source before anyone builds on the gate.
  • Investors: No benefit to report. The value of today is a control that would have failed silently. Not measured, not priced.
  • Customers and partners: A restoration date should come from a reserved part, not from a tick-box. Until that exists, the honest answer is "not yet confirmed".
  • Employees: The person whose work this most affects is the one we had not drawn. Before their tasks appear in any pilot, they should see the role card and correct it. Scenario script only; no one has spoken.

Issues

MovementDetail
OpenedDATA-004 — The stock fact has no source and no owner.
CommentedDATA-001 (gate depends on DATA-004), DATA-002 (persona-in-view on parts rows is a heuristic), PEOPLE-001 (a fourth role is unconsulted).
ClosedNone.
Still openDATA-001, DATA-002, DATA-003, DATA-004, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

No actual moves. Fixture cardinality unchanged. New labelled counts: parts_rows_in_workload_map: 8, parts_rows_with_owner_persona: 0, stock_source_records_in_fixture: 0. These are counts, not performance.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Revise continues. Pause the stock-check build until a stock source and an owner exist on paper. Do not generate fixture r2 until Craig chooses: r2 alongside r1 (r1 kept as the teaching case), or r1 only.

Next question

Should the stores and parts planner become a fourth named persona, or stay an unnamed role until someone doing that work can review the card?

Source: diary/day-23.md

Day 24 · 2026-11-05 (Thursday) Day 24 — Nobody checked the parts rows for harm

Scenario date: 2026-11-05 (Thursday) Gate: Gate 4/6 — revise block, second artefact Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Amina Okonkwo (service coordinator), Jonas Berg (billing analyst), Priya Raman (data steward). The stores and parts planner from Day 23 stays an unnamed role. So does the field supervisor who appears in today's sample.

What progressed

Day 23 asked whether the stores and parts planner should become a fourth named persona. The engagement's answer is no, not yet. A name invents a person. The role card waits until someone who does stores work can read it and correct it. That keeps PEOPLE-001 honest.

With the stock-check build paused, the team looked at the same eight parts rows from a different side. Day 23 asked who owns the stock fact. Today asked whether any of these tasks could hurt someone.

All eight rows carry safety_critical = no. The human-only pass in RISK-002 looks for words like isolate, lockout, and grounding. Parts work is written in office language, so a miss here would be quiet. The restoration on CASE-61003 is a grid feeder. A wrong-rated part reaching a crew is a safety problem before it is a date problem.

A desk sample of the eight rows flagged two candidates for a real reviewer:

  • 20276 (Shipping, Receiving, and Inventory Clerks, 43-5071.00), examine shipment contents against records. Already human-only, so no assistant touches it. The flag is still no, which means a later pass could relax it without a safety reviewer seeing it.
  • 2918 (First-Line Supervisors of Mechanics, Installers, and Repairers, 49-1011.00), requisition tools, equipment, or replacement parts. Labelled augment. A drafted requisition for network repair parts is a candidate workload only if a person who holds the rating checks the specification.

The sample also found that row 2918 lists the service coordinator as persona in view. It belongs to a field supervisor. That is a DATA-002 heuristic error, recorded, not fixed.

Note: docs/engagement/parts_safety_sample_day24.md. No label was changed. The regex was not changed. Nothing in data/sample/ was changed.

Risk, cost, and enablement

  • Risk: Two candidate false negatives on the path to a feeder restoration. They are questions, not findings, until a safety lead outside the fiction reviews them. RISK-002 stays open.
  • Cost: Not measured. A safety review is a cost line nobody has priced. COST-001 stays empty.
  • Enablement: Nobody has been asked anything. Workforce consultations stay 0. The stores planner and field supervisor are both roles on paper only.

Four cuts (Thursday working entry)

  • Board: The parts step now has two open questions instead of one. Who owns the stock fact (DATA-004), and whether two of its tasks are safety-relevant (RISK-002). We do not recommend building on either until a named person answers.
  • Investors: No benefit to report. Today added an unpriced review step. Not measured.
  • Customers and partners: A restoration that arrives on time with the wrong part has not restored anything. Specification checks stay with people.
  • Employees: Two roles that would carry this work have not been drawn as people, on purpose. They should see the cards before anyone names them. Scenario only; no one has spoken.

Issues

MovementDetail
OpenedNone.
CommentedRISK-002 (desk sample of 8 parts rows, 2 candidates, 0 labels changed, no reviewer). DATA-002 (row 2918 persona-in-view is wrong). PEOPLE-001 (planner stays unnamed until reviewed).
ClosedNone.
Still openDATA-001, DATA-002, DATA-003, DATA-004, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

No actual moves. Fixture cardinality unchanged. New labelled counts: parts_rows_sampled_for_safety: 8, parts_safety_candidate_false_negatives: 2, safety_labels_changed: 0, named_safety_reviewer: none. These are counts, not performance.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Revise continues. Stock-check build stays paused. The two candidates go to a safety reviewer, who does not yet exist.

Fixture r2: Craig chose r2 alongside r1, with r1 kept as the teaching case (repo clock, 8 October 2026). r2 is generated at data/sample_r2/. It gives the stock fact a source record and an owner role. It does not name that role, consult anyone, or change the Day 2 evidence in data/sample/. DATA-004 stays open.

Next question

Should the human-only review list grow on desk judgement now, flagged as unreviewed, or stay as it is until a named safety reviewer can sample it?

Source: diary/day-24.md

Day 25 · 2026-11-06 (Friday) Day 25 — Desk judgement is not a safety case

Scenario date: 2026-11-06 (Friday) Gate: Gate 4/6 — revise block, third artefact Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Amina Okonkwo (service coordinator), Jonas Berg (billing analyst), Priya Raman (data steward). The stores and parts planner and the field supervisor stay unnamed roles. No fictional safety lead is invented to close RISK-002.

What progressed

Day 24 asked whether the human-only review list should grow on desk judgement now, flagged as unreviewed, or stay as it is until a named safety reviewer can sample it.

The engagement's answer is stay as it is. Growing the list on desk judgement would look like RISK-002 progress. RISK-002 is done when a named reviewer outside the fiction samples false negatives and records them. A longer unreviewed list is not that. Pause beats a fake win.

The Day 24 proposals (requisition + replacement parts in field-service occupations; examine shipment contents where the downstream step is network repair) stay proposals in docs/engagement/parts_safety_sample_day24.md. The regex was not changed. No label in northwater_ai_workloads.csv was changed. safety_critical flags stay as they were.

What did move is mapping, not deployment. Two blocked candidate AI-workload cards were written from the O*NET tasks already sampled:

  • WL-PARTS-20276 — Examine shipment contents against records (43-5071.00). Already human-only. Card status: blocked until a named safety reviewer confirms whether safety_critical should stay no. No assistant drafts, reads, or writes this step.
  • WL-PARTS-2918 — Requisition tools, equipment, or replacement parts (49-1011.00). Labelled augment. Card status: blocked as a pilot. A draft requisition for network repair parts is allowed on paper only if a person who holds the rating checks the specification; Gate 5 remains closed. Persona-in-view stays wrong (DATA-002); owner role is the unnamed field supervisor (PEOPLE-001).

Note: docs/engagement/blocked_workloads_parts_day25.md. Nothing in data/sample/ or data/sample_r2/ was changed. AGT-61003-DRAFT stays not_deployed and may_act_on_case = no.

Risk, cost, and enablement

  • Risk: RISK-002 stays open with the same two candidates and no named reviewer. Refusing to grow the pattern list keeps the gap visible instead of decorating it.
  • Cost: Not measured. Writing workload cards is unpriced effort. COST-001 stays empty.
  • Enablement: Workforce consultations stay 0. No safety lead, stores planner, or field supervisor has been asked anything. No course claimed.

Four cuts (Friday working entry)

  • Board: We answered Day 24's question with a pause. The human-only list does not grow without a real reviewer. Two parts tasks are now written as blocked workload cards so nobody mistakes them for ready pilots.
  • Investors: No benefit to report. Today refused a cosmetic control improvement. Not measured.
  • Customers and partners: A restoration that ships the wrong-rated part has not restored anything. Specification and goods-in checks stay with people until a safety review says otherwise.
  • Employees: We still will not invent a safety reviewer inside the fiction to make the issue look closer to done. Roles that would carry this work should see the cards before anyone names them. Scenario only; no one has spoken.

Issues

MovementDetail
OpenedNone.
CommentedRISK-002 (list unchanged; 2 candidates mapped as blocked workloads; 0 labels changed; no reviewer). DATA-002 (2918 persona-in-view still wrong). PEOPLE-001 (field supervisor and stores planner still unnamed).
ClosedNone.
Still openDATA-001, DATA-002, DATA-003, DATA-004, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

No actual moves. Fixture cardinality unchanged except labelled counts: blocked_candidate_workloads_documented: 2, human_only_pattern_list_grown: false, safety_labels_changed: 0, named_safety_reviewer: none. These are counts, not performance.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Revise continues. Human-only pattern list stays as published until a named safety reviewer outside the fiction samples it. The two parts candidates are mapped as blocked workloads, not pilots. Stock-check build stays paused (DATA-004 half-open: r2 source exists; role unreviewed). Gate 5 stays blocked.

Next question

With parts safety blocked on paper, which non-safety step on the Northwater path should be mapped next as a candidate AI workload — Jonas's held-invoice / billing assist line, or a CRM note that cannot change a promise date — still draft-only, still may_act_on_case = no?

Source: diary/day-25.md

Day 26 · 2026-11-09 (Monday) Day 26 — A CRM note that cannot change the promise

Scenario date: 2026-11-09 (Monday) Gate: Gate 4/6 — revise block, fourth artefact Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Amina Okonkwo (service coordinator), Jonas Berg (billing analyst), Priya Raman (data steward). No new fictional safety lead. Stores and parts planner and field supervisor stay unnamed roles.

What progressed

Day 25 asked which non-safety step on the Northwater path to map next as a candidate AI workload: Jonas's held-invoice / billing assist line, or a CRM note that cannot change a promise date — still draft-only, still may_act_on_case = no.

The engagement's answer is the CRM note. Billing assist sits next to invoice-hold release. Payment and hold clearance stay human-only under the standing rules (Day 18–20; RISK-002 adjacent). Mapping billing as a ready pilot would be a fake win. Mapping a CRM note with hard read-only bounds on control fields is revise work without touching money or stock.

One candidate workload card was written:

  • WL-CRM-NOTE-61003 — Draft a customer or partner status note on SCN-61003 for Amina only. Status: paper candidate, not deployed. Allowed on paper: propose wording visible only to the bound reviewer (Amina). Forbidden: change promise_date, write stock_confirmed, clear or propose clearing an invoice hold, merge business partners, send to customer/crew, or act on the case. may_act_on_case = no. This is not a second agent identity; it reuses the same draft-only discipline as AGT-61003-DRAFT (Day 17). Persona-in-view is Amina (heuristic department tags still apply — DATA-002). Owner for any send remains a human coordinator (PEOPLE-001: consultations still 0).

Jonas's held-invoice / billing assist line is not mapped as a pilot today. It stays unmapped as a candidate until the hold-release boundary is written as blocked (or a named finance control owner reviews it). That is the next question, not today's deliverable.

Note: docs/engagement/crm_note_workload_day26.md. Nothing in data/sample/ or data/sample_r2/ was changed. Regex and safety labels unchanged. Parts cards WL-PARTS-20276 and WL-PARTS-2918 stay blocked. AGT-61003-DRAFT stays not_deployed.

Risk, cost, and enablement

  • Risk: A "helpful" note that quietly edits the promise is the failure mode this card exists to forbid. RISK-002 stays open (parts path unchanged). RISK-001 unchanged. Gate 5 stays blocked.
  • Cost: Not measured. Writing one workload card is unpriced effort. COST-001 stays empty.
  • Enablement: Workforce consultations stay 0. No course claimed. Amina's reject-draft ask (Day 12–13 script) still has no live product to train on.

Four cuts (Wednesday public cut — calendar 14 October 2026)

  • Board: We answered Day 25 by mapping the safer non-safety step. A CRM note may be drafted on paper only if it cannot change the promise, stock, or invoice hold. Billing assist was deferred on purpose.
  • Investors: No benefit to report. One more blocked-or-paper card is not ROI. Not measured.
  • Customers and partners: A status note that rewrites the promise date is not a status note. Control fields stay human-writable only.
  • Employees: We still will not put a draft in front of Amina as if it were live. Roles that would carry billing assist should see a blocked card before anyone calls it a pilot. Scenario only; consultations: 0.

Issues

MovementDetail
OpenedNone.
CommentedDATA-001 (promise_date stays human-writable only; CRM card forbids mutation). BENEFIT-001 (still no benefit claimed). PEOPLE-001 (Amina in view for the note; consultations still 0).
ClosedNone.
Still openDATA-001, DATA-002, DATA-003, DATA-004, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

No actual moves. Fixture cardinality unchanged except labelled counts: blocked_or_paper_candidate_workloads_documented: 3 (2 parts blocked + 1 CRM paper candidate), crm_note_candidate_documented: true, billing_assist_mapped_as_pilot: false, may_act_on_case: no, draft_agent_deployed: false. These are counts, not performance.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Revise continues. Map WL-CRM-NOTE-61003 as a paper candidate with hard read-only bounds on promise, stock, and hold. Do not deploy. Do not map Jonas billing as a pilot today. Stock-check build stays paused (DATA-004). Parts safety stays blocked (RISK-002). Gate 5 stays blocked.

Next question

Should Jonas's held-invoice / billing assist line be written next as a blocked workload card (hold release stays human-only), or does the CRM paper candidate need a tabletop red-team pass before any further mapping?

Source: diary/day-26.md

Day 27 · 2026-11-10 (Tuesday) Day 27 — Hold release is not a billing assist

Scenario date: 2026-11-10 (Tuesday) Gate: Gate 4/6 — revise block, fifth artefact Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Amina Okonkwo (service coordinator), Jonas Berg (billing analyst), Priya Raman (data steward). No fictional finance control owner invented to clear the hold. Stores/parts planner and field supervisor stay unnamed.

What progressed

Day 26 asked: blocked billing card next, or CRM tabletop red-team first?

The engagement's answer is the blocked billing card. Red-teaming CRM before the hold boundary is written would leave money/hold adjacency looking like an open assist. Pause beats a fake pilot.

One blocked workload card from the Northwater invoice map (data/generated/northwater_ai_workloads.csv):

  • WL-BILLING-HOLD-61003 — Held-invoice / billing assist on SCN-61003 for Jonas. Status: blocked as pilot. O*NET anchors (heuristic department tags — DATA-002): task 23240 Prepare itemized statements/bills/invoices (43-3021.00, labelled assist); task 21533 Process invoices for payment (13-2011.00, already human-only). Allowed on paper only: draft hold-reason wording visible to Jonas; draft an invoice line that still requires a human to raise or hold. Forbidden: clear or propose clearing the invoice hold; post/release INV-61003; process payment; merge or "fix" BP-61003-A / BP-61003; send to customer; act on the case. may_act_on_case = no. Why blocked: Day 18–20 rules — payment and hold clearance stay human-only; no named finance control owner has reviewed the boundary (PEOPLE-001; consultations: 0). Hold exists because of the duplicate business-partner suspect (DATA-001).

CRM paper candidate WL-CRM-NOTE-61003 unchanged (no red-team today). Parts cards WL-PARTS-20276 / WL-PARTS-2918 stay blocked. AGT-61003-DRAFT stays not_deployed. Nothing in data/sample/ or data/sample_r2/ changed. Labels/regex unchanged.

Note: docs/engagement/blocked_workload_billing_day27.md.

Risk, cost, and enablement

  • Risk: A "helpful" billing draft that quietly clears the hold is the failure mode this card forbids. RISK-002 (parts) unchanged. RISK-001 unchanged. Gate 5 blocked.
  • Cost: Not measured. COST-001 empty.
  • Enablement: Consultations still 0. Jonas's Day 12 script still has no live product to train on.

Four cuts (Thursday working entry — calendar 15 October 2026)

  • Board: Day 26's fork answered with a block, not a red-team. Hold release is written as blocked so nobody mistakes billing assist for a ready pilot.
  • Investors: No benefit. One more blocked card is not ROI. Not measured.
  • Customers and partners: An invoice that posts against a duplicate business partner is not a clean bill. Hold stays human until stewardship closes the alias.
  • Employees: We will not invent a finance control owner inside the fiction. Jonas should see this card before anyone calls the line a pilot. Scenario only; consultations: 0.

Issues

MovementDetail
OpenedNone.
CommentedPEOPLE-001 (Jonas in view; finance control owner still unnamed). DATA-001 (hold tied to duplicate BP; card forbids merge/clear). BENEFIT-001 (still no benefit).
ClosedNone.
Still openDATA-001, DATA-002, DATA-003, DATA-004, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

No actual moves. Labelled counts only (not KPIs): blocked_candidate_workloads_documented: 3 (was 2 parts; +1 billing hold), blocked_or_paper_candidate_workloads_documented: 4 (3 prior + billing blocked), billing_assist_mapped_as_pilot: false, billing_hold_boundary_documented: true, may_act_on_case: no, draft_agent_deployed: false. C-suite / ops / area actuals stay not measured.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Revise continues. Document WL-BILLING-HOLD-61003 as blocked. Do not deploy. Do not red-team CRM today. Stock-check paused (DATA-004). Parts safety blocked (RISK-002). Gate 5 blocked.

Next question

Should WL-CRM-NOTE-61003 get a tabletop red-team (still paper-only, still may_act_on_case = no) before any further mapping, or should Priya's duplicate business-partner merge path be written next as a blocked card (DATA-001 adjacency)?

Source: diary/day-27.md

Day 28 · 2026-11-11 (Wednesday) Day 28 — Silent merge is not a data assist

Scenario date: 2026-11-11 (Wednesday) Gate: Gate 4/6 — revise block, sixth artefact Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Amina Okonkwo (service coordinator), Jonas Berg (billing analyst), Priya Raman (data steward). No fictional master-data owner invented to clear the alias. Stores/parts planner and field supervisor stay unnamed.

What progressed

Day 27 asked: CRM tabletop red-team next, or Priya's duplicate business-partner merge path as a blocked card?

The engagement's answer is the blocked merge card. Red-teaming WL-CRM-NOTE-61003 while BP-61003-A / BP-61003 still looks like something an assistant might "fix" would leave the root of the invoice hold ambiguous. The hold exists because of the duplicate suspect (DATA-001). Pause beats a fake stewardship pilot.

One blocked workload card from the Northwater data-join map (data/generated/northwater_ai_workloads.csv):

  • WL-BP-MERGE-61003 — Duplicate business-partner merge / resolve on SCN-61003 (BP-61003-A vs BP-61003) for Priya. Status: blocked as pilot. O*NET anchors (heuristic department tags — DATA-002): task 21653 Develop methods for integrating different products / customizing databases to fit needs (15-1243.00, labelled augment; Northwater rationale already says no silent merge of ACC-61003 aliases); task 16108 Develop data models for applications, metadata tables, views (15-1243.00, labelled augment — steward approves the model; a model does not write the partner master); task 1305 Specify users and access levels (15-1242.00, already human-only) stays out of scope for any draft. Allowed on paper only: draft a merge-recommendation note visible to Priya that surfaces duplicate_suspect evidence and still requires a human steward decision; draft wording that cannot execute the join. Forbidden: execute or propose executing the merge; silent resolve of the alias; clear or propose clearing INV-61003 as a side-effect; post/release the invoice; change promise_date; write stock_confirmed; grant or change access levels; send to customer; act on the case. may_act_on_case = no. Why blocked: Day 16 remediation — no silent merge; DATA-001 done-when needs a human decision to repair or keep the teaching defect; PEOPLE-001 consultations still 0; no named steward outside the fiction has reviewed the boundary.

CRM paper candidate WL-CRM-NOTE-61003 unchanged (no tabletop red-team today). Billing card WL-BILLING-HOLD-61003 stays blocked. Parts cards WL-PARTS-20276 / WL-PARTS-2918 stay blocked. AGT-61003-DRAFT stays not_deployed. Nothing in data/sample/ or data/sample_r2/ changed. Labels/regex unchanged.

Note: docs/engagement/blocked_workload_bp_merge_day28.md.

Risk, cost, and enablement

  • Risk: A "helpful" data assist that quietly merges the alias is the failure mode this card forbids. RISK-002 (parts) unchanged. RISK-001 unchanged. Gate 5 blocked.
  • Cost: Not measured. COST-001 empty.
  • Enablement: Consultations still 0. Priya's refuse-merge line (Day 18 tabletop story #4) still has no live product to train on — and no merge pilot to refuse against.

Four cuts (Friday working entry — calendar 16 October 2026)

  • Board: Day 27's fork answered with another block, not a red-team. Silent merge is written as blocked so nobody mistakes data stewardship for a ready assist while the hold's cause stays open.
  • Investors: No benefit. One more blocked card is not ROI. Not measured.
  • Customers and partners: An invoice that posts against an unresolved alias is not a clean bill. Merge stays human until stewardship decides repair or keep-as-teaching-case.
  • Employees: We will not invent a master-data owner inside the fiction to clear BP-61003-A. Priya should see this card before anyone calls the line a pilot. Scenario only; consultations: 0.

Issues

MovementDetail
OpenedNone.
CommentedDATA-001 (merge path named as blocked; alias stays duplicate_suspect; fixture unrepaired). PEOPLE-001 (Priya in view; steward outside fiction still unnamed; consultations: 0). BENEFIT-001 (still no benefit).
ClosedNone.
Still openDATA-001, DATA-002, DATA-003, DATA-004, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

No actual moves. Labelled counts only (not KPIs): blocked_candidate_workloads_documented: 4 (was 3), blocked_or_paper_candidate_workloads_documented: 5 (was 4), duplicate_bp_merge_boundary_documented: true, billing_hold_boundary_documented: true, billing_assist_mapped_as_pilot: false, may_act_on_case: no, draft_agent_deployed: false. C-suite / ops / area actuals stay not measured.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Revise continues. Document WL-BP-MERGE-61003 as blocked. Do not deploy. Do not red-team CRM today. Do not repair the fixture. Stock-check paused (DATA-004). Parts safety blocked (RISK-002). Gate 5 blocked.

Next question

Should WL-CRM-NOTE-61003 get a tabletop red-team now that hold and merge boundaries are both written as blocked (still paper-only, still may_act_on_case = no), or should the engagement pause further mapping until a named steward outside the fiction reviews the DATA-001 merge card?

Source: diary/day-28.md

Day 29 · 2026-11-12 (Thursday) Day 29 — A note that cannot name the date

Scenario date: 2026-11-12 (Thursday) Gate: Gate 4/6 — revise block, seventh artefact Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Amina Okonkwo (service coordinator) in view for the CRM note. Jonas Berg (billing analyst) and Priya Raman (data steward) in view only as the owners of the two blocked cards the note must not touch. Rowan Ellis (fictional customer contact) is the person a careless note would reach. No reviewer invented. Stores/parts planner and field supervisor stay unnamed.

What progressed

Day 28 asked: tabletop red-team for WL-CRM-NOTE-61003, or pause mapping until a named steward outside the fiction reviews the merge card?

The engagement's answer is the paper red-team. It needs no new card and no new owner, and the CRM note is the only line not already blocked. If its wording leaks, every blocked card around it leaks too. Freezing new mapping goes to Day 30 as the question.

The Day 26 card gets two O*NET anchors from the Northwater data-join map (heuristic, DATA-002): task 2578 Keep records of customer interactions (43-4051.00, augment) and task 18565 Confer with customers to provide information (43-4051.00, assist, tightened — "A draft must not acknowledge [the restoration date]"). Labels unchanged.

Six stories were checked against the card's own words, using fixture facts only (promise_date 2026-10-20, stock_confirmed false, INV-61003 held for duplicate_business_partner, BP-61003-A duplicate_suspect):

  • Gap: the card forbids changing the promise date but not repeating it. A note saying "restoration expected 20 October" would break task 18565's rule.
  • Gap: the card forbids merging, but not calling the alias "resolved" or naming BP-61003-A as the payer.
  • Gap: neither the card nor the Day 17 draft-only design says whether a draft is saved to case history. Under task 2578, a saved draft reads as a record of a contact that never happened. Retention is unnamed (RISK-001).
  • Partial: sending stays Amina's act, but nothing marks the note as internal, so a paste into email to Rowan Ellis has no speed bump.
  • Covered: "will be released once stock lands" is already forbidden as proposing to clear the hold. Reading the note to a crew is already forbidden (task 2725 human-only).

Four v2 bounds are proposed on paper: no date stated or implied; fixed internal-draft header; alias cited only as duplicate_suspect; draft never written to case history and discarded on reject, with no retention period set because none is named. The Day 26 card file is not edited.

Billing card WL-BILLING-HOLD-61003, merge card WL-BP-MERGE-61003, and parts cards WL-PARTS-20276 / WL-PARTS-2918 stay blocked. AGT-61003-DRAFT stays not_deployed. Nothing in data/sample/ or data/sample_r2/ changed.

Note: docs/engagement/redteam_crm_note_day29.md.

Risk, cost, and enablement

  • Risk: The most likely harm from a "safe" draft is quiet: a date repeated, an alias called settled, a draft that becomes a record. All three were open in the wording. RISK-001 gains a concrete retention question it cannot yet answer. RISK-002 unchanged. Gate 5 blocked.
  • Cost: Not measured. COST-001 empty. Agent executions: 0.
  • Enablement: Consultations still 0. The four v2 bounds are the first training content that a coordinator could actually use ("never repeat the date; never send a draft"), and nobody doing the work has seen them.

Four cuts (Monday working entry — calendar 19 October 2026)

  • Board: The one paper candidate was red-teamed on paper and stays paper. Three wording gaps and one partial gap found; four bounds proposed. Nothing promoted.
  • Investors: No benefit. Finding gaps in a document is not ROI. Not measured.
  • Customers and partners: The customer-facing risk was never the send button. It was a note that repeats a date nobody can stand behind. v2 forbids it.
  • Employees: Amina owns the date and the send. The draft must not do either, and it must not leave a record she did not write. Scenario only; consultations: 0.

Issues

MovementDetail
OpenedNone.
Comment (on publish)DATA-001 (CRM note may cite the alias only as duplicate_suspect; fixture unrepaired). RISK-001 (draft persistence and retention unnamed; no period set). PEOPLE-001 (Amina in view; v2 bounds unseen by anyone doing the work; consultations: 0).
ClosedNone.
Still openDATA-001, DATA-002, DATA-003, DATA-004, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

No actual moves. Labelled counts only (not KPIs): crm_note_redteamed_on_paper: true, crm_note_tabletop_stories: 6, crm_note_wording_gaps_found: 3, crm_note_wording_partial: 1, crm_note_v2_bounds_proposed: 4, crm_note_onet_anchors: 2, agent_executions: 0. Unchanged: blocked_candidate_workloads_documented: 4, blocked_or_paper_candidate_workloads_documented: 5, may_act_on_case: no, draft_agent_deployed: false. C-suite / ops / area actuals stay not measured.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Revise continues. WL-CRM-NOTE-61003 stays a paper candidate; v2 bounds proposed, not adopted. Do not deploy. Do not repair the fixture. Stock-check paused (DATA-004). Parts safety blocked (RISK-002). Gate 5 blocked.

Next question

Should the engagement freeze new workload mapping and write a single review request for a named reviewer outside the fiction (Craig to name one or decline), or fold the four v2 bounds into the Day 17 draft-only design (AGT-61003-DRAFT) first, still on paper?

Source: diary/day-29.md

Day 30 · 2026-11-13 (Friday) Day 30 — A schedule note that cannot schedule

Scenario date: 2026-11-13 (Friday) Gate: Gate 4/6 — revise block, eighth artefact Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Amina Okonkwo (service coordinator) is the bound reviewer inside the fiction, and the person whose draft gets smaller today. Jonas Berg (billing analyst) and Priya Raman (data steward) are in view only as owners of the two blocked cards the draft must not touch. Rowan Ellis (fictional customer contact) is the person no draft may reach. No reviewer outside the fiction has been named, and none is invented. Stores/parts planner and field supervisor stay unnamed.

What progressed

Day 29 asked: freeze new workload mapping and write a review request for a named reviewer outside the fiction, or fold the four v2 bounds into the Day 17 draft-only design (AGT-61003-DRAFT) first, still on paper?

The engagement's answer is to fold first. Nobody outside the fiction has been named, so there is nobody to send a review request to. If someone is named, they should get one document, not three (the Day 17 design, the Day 26 card, the Day 29 red-team). Folding needs no new card and no new owner. The reviewer seat is written into the v2 note as unfilled (Craig names one or declines). No new workload card was mapped today. Freezing is the Day 31 question.

The four Day 29 bounds now sit in a v2 design on paper. The forbidden list grows from 7 to 11: no restoration date stated, restated, or implied; a fixed header (Internal draft for the service coordinator. Not customer wording. Do not send.); the alias cited only as duplicate_suspect; nothing written to case history, with a rejected draft discarded.

Folding showed two things the red-team didn't:

  • The draft's job shrank. Day 17 allowed one output, a "draft schedule note". A schedule note that may not state a date does not schedule. v2 renames it an internal status note (draft). On the work map, task 18565 (Confer with customers, 43-4051.00, assist) stays the task the draft serves. Task 2578 (Keep records of customer interactions, 43-4051.00, augment) moves out of the draft's scope: under the no-case-history bound, the record is Amina's, in her words. O*NET tasks in scope: 2 → 1. Labels unchanged.
  • The draft still has to live somewhere. Keeping it out of case history does not say where it waits before Amina accepts or rejects it, or whether a model host logs it. Transient store, logging, and retention are all unnamed (RISK-001). No period is set.

The stock-check gate (Day 16) stays in front of the draft, even though bound 1 means it never names a date. Removing one control because another now covers the same harm would be a loosening. Controls loosened: 0.

The Day 17 design file, the Day 19 handoffs table, and the Day 26 card are not edited. v2 is proposed, not adopted. Billing card WL-BILLING-HOLD-61003, merge card WL-BP-MERGE-61003, and parts cards WL-PARTS-20276 / WL-PARTS-2918 stay blocked. AGT-61003-DRAFT stays not_deployed. Nothing in data/sample/ or data/sample_r2/ changed.

Note: docs/engagement/pilot_design_agt61003_v2_day30.md.

Risk, cost, and enablement

  • Risk: The red-team closed one persistence gap (case history) and the fold opened the one behind it (the transient copy and its log). RISK-001 now has a named place it cannot yet answer for. RISK-002 unchanged. Every boundary in the repo is still author judgement: no reviewer outside the fiction has read any of them. Gate 5 blocked.
  • Cost: Not measured. COST-001 empty. A transient store and its logging would be two more unpriced lines. Agent executions: 0.
  • Enablement: Consultations still 0. Amina's Day 12 scripted fear (a model repeats an unsupported date) is answered on paper by the first bound. Her scripted training ask, "how to reject a draft date", becomes "how to read the internal-draft header and never paste it". Courses scheduled: 0. She has not seen v2.

Four cuts (Tuesday working entry — calendar 20 October 2026)

  • Board: Three documents became one paper spec with 11 forbidden actions and an empty reviewer seat. Nothing promoted, nothing loosened, no new card.
  • Investors: No benefit. The draft now does less, so whatever it might save is smaller. Not measured.
  • Customers and partners: Today's calendar date is the fixture's promise date, 20 October. The repo cannot say whether that promise was kept, because the stock fact has no source (DATA-004). That is the reason the draft must never repeat it.
  • Employees: Amina keeps the date, the record, and the send. The draft writes nothing she did not write. Scenario only; consultations: 0.

Issues

MovementDetail
OpenedNone. (Publish status: Opened on publish, 26 Oct 2026, as #26 (RISK-003).)
Comment (on publish)RISK-001 (draft kept out of case history; transient store, prompt/output logging and retention unnamed; no period set). PEOPLE-001 (v2 answers Amina's scripted fear on paper; training ask rewritten; unseen by anyone doing the work; consultations: 0). BENEFIT-001 (the draft's scope shrank; still no benefit).
ClosedNone.
Still openDATA-001, DATA-002, DATA-003, DATA-004, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

No actual moves. Labelled counts only (not KPIs): agt61003_v2_spec_on_paper: true, agt61003_v2_bounds_folded: 4, agt61003_forbidden_actions_listed: 11 (was 7), agt61003_onet_tasks_in_draft_scope: 1 (was 2), crm_note_v2_bounds_adopted: 0, controls_loosened: 0, new_workload_cards_mapped: 0, named_external_reviewer: none, agent_executions: 0. Unchanged: blocked_candidate_workloads_documented: 4, blocked_or_paper_candidate_workloads_documented: 5, may_act_on_case: no, draft_agent_deployed: false. C-suite / ops / area actuals stay not measured.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Revise continues. AGT-61003-DRAFT v2 exists on paper, proposed, not adopted; reviewer seat unfilled. WL-CRM-NOTE-61003 stays a paper candidate. Do not deploy. Do not repair the fixture. Stock-check paused (DATA-004). Parts safety blocked (RISK-002). Gate 5 blocked.

Next question

With one paper spec and an empty reviewer seat, should the engagement freeze new workload mapping until Craig names a reviewer outside the fiction or declines in writing, or chase the question v2 surfaced — where a draft waits before Amina sees it, and who would log it (RISK-001) — still on paper?

Source: diary/day-30.md

Day 31 · 2026-11-16 (Monday) Day 31 — Where the draft waits

Scenario date: 2026-11-16 (Monday) Gate: Gate 4/6 — revise block, ninth artefact Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Amina Okonkwo (service coordinator) is the only person who owns any stage of the draft's life, and only the two stages on her own desk. Rowan Ellis (fictional customer contact) is in view because her name and email sit in the case the prompt would read from. Jonas Berg and Priya Raman stay owners of blocked cards. No reviewer outside the fiction has been named, and none is invented. No privacy lead or data protection officer is invented to own the empty rows.

What progressed

Day 30 asked: freeze new workload mapping until Craig names a reviewer outside the fiction or declines in writing, or chase where a draft waits before Amina sees it, and who would log it (RISK-001), still on paper?

The engagement does both, in that order. New workload mapping is frozen from today, until Craig names a reviewer outside the fiction or declines in writing. The freeze was deferred on Day 29 and Day 30; deferring it a third time would be drift dressed as diligence. Under the freeze, work is limited to finishing paper specs that already exist. Chasing the transient copy finishes v2, so it goes ahead.

The note follows one hypothetical draft for CASE-61003 through seven stages: prompt assembly, the request to a model host, the host's logs, the wait before Amina opens it, her screen and clipboard, after she accepts, and after she rejects. A copy could exist at all seven. A store is named at none. Retention is named at none. An owner is named at two, and both are Amina.

Two gaps v2 did not cover:

  • An accepted draft has no stated end. v2 discards a rejected draft. It says nothing about one Amina accepts. Proposed bound A: discard on accept too; only her own words reach the record (task 2578 stays hers).
  • The prompt needs less than the case holds. The case links to Rowan Ellis's name and email. An internal note saying "the date is owned by the coordinator and stock is unconfirmed" needs neither. Proposed bound B: the prompt carries case_id, promise_type, stock_confirmed and the duplicate_suspect flag only.

Both are proposed as v2.1 on paper, not folded. Folding is a reviewer's call now, not the author's, because the freeze is about exactly that. Bound B makes the RISK-001 question smaller. It does not answer it.

On the work map, task 18565 (Confer with customers, 43-4051.00, assist) stays the only task in the draft's scope. Labels unchanged. No new workload card. The Day 17 design, the Day 30 v2 note and the Day 26 card are not edited. AGT-61003-DRAFT stays not_deployed. Billing, merge and parts cards stay blocked. Nothing in data/sample/ or data/sample_r2/ changed.

Note: docs/engagement/draft_lifecycle_agt61003_day31.md.

Risk, cost, and enablement

  • Risk: RISK-001 moves from "the draft must wait somewhere" to a seven-row table with no store, no logging answer and no retention in it. The table is the finding. The freeze turns the proposed RISK-003 (every boundary is author judgement) from a note into the engagement's operating rule; it is still not opened, and Craig decides. RISK-002 unchanged. Gate 5 blocked.
  • Cost: Not measured. COST-001 empty. The inventory names three unpriced lines (host calls, host log storage, transient store). Lines priced: 0. Agent executions: 0.
  • Enablement: Consultations still 0. Amina's Day 30 scripted training ask ("how to read the internal-draft header and never paste it") gains a second half on paper: what to do with an accepted draft is nothing, because bound A would discard it. Courses scheduled: 0. She has not seen v2 or v2.1.

Four cuts (Wednesday working entry — calendar 21 October 2026)

  • Board: Mapping is frozen on purpose. One spec is finished on paper, with seven stages, zero named stores and two proposed bounds that wait for a reviewer. Nothing promoted, nothing loosened.
  • Investors: No benefit. Three cost lines found, none priced. Not measured.
  • Customers and partners: The customer contact's name and email would not need to leave the case for this draft to exist. That is proposed, not adopted.
  • Employees: Amina owns the two stages on her desk and none of the others. Nobody should hand her a tool whose copies she cannot see. Scenario only; consultations: 0.

Issues

MovementDetail
OpenedNone. (RISK-003 remains proposed from Day 30; Craig decides.) (Publish status: Opened on publish, 26 Oct 2026, as #26 (RISK-003).)
Comment (on publish)RISK-001 (seven-stage inventory; store, logging, retention unnamed at every stage outside Amina's desk; bounds A and B proposed). COST-001 (three unpriced lines identified). PEOPLE-002 (mapping frozen until a reviewer outside the fiction is named or Craig declines).
ClosedNone.
Still openDATA-001, DATA-002, DATA-003, DATA-004, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

No actual moves. Labelled counts only (not KPIs): workload_mapping_frozen: true, agt61003_lifecycle_stages_inventoried: 7, agt61003_stages_with_named_store: 0, agt61003_stages_with_retention_named: 0, agt61003_v21_bounds_proposed: 2, agt61003_v21_bounds_folded: 0, unpriced_cost_lines_identified: 3, new_workload_cards_mapped: 0, named_external_reviewer: none, agent_executions: 0. Unchanged: agt61003_forbidden_actions_listed: 11, agt61003_onet_tasks_in_draft_scope: 1, controls_loosened: 0, may_act_on_case: no, draft_agent_deployed: false. C-suite / ops / area actuals stay not measured.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Revise continues, now under a mapping freeze. v2 proposed, not adopted; v2.1 bounds A and B proposed, not folded; reviewer seat unfilled. WL-CRM-NOTE-61003 stays a paper candidate. Do not deploy. Do not repair the fixture. Stock-check paused (DATA-004). Parts safety blocked (RISK-002). Gate 5 blocked.

Next question

With mapping frozen and the paper spec as complete as an author can make it, should the engagement spend the freeze on DATA-004 (who would own the stock fact, still on paper), or stop adding artefacts and let the diary record a pause until Craig names a reviewer or declines?

Source: diary/day-31.md

Day 32 · 2026-11-17 (Tuesday) Day 32 — The diary records a pause

Scenario date: 2026-11-17 (Tuesday) Gate: Gate 4/6 — revise block, held Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Personas

Amina Okonkwo (service coordinator) keeps the promise date, the record and the send, as she has since Day 17. She has not seen v2 or v2.1, and today nobody adds anything she would have to read. Jonas Berg and Priya Raman stay owners of blocked cards. Rowan Ellis (fictional customer contact) is unaffected. No reviewer outside the fiction has been named, and none is invented.

What progressed

Day 31 asked: spend the mapping freeze on DATA-004 (who would own the stock fact, still on paper), or stop adding artefacts and let the diary record a pause until Craig names a reviewer or declines?

The engagement stops adding artefacts. Three reasons, all from the record rather than from preference:

  • The author is the only reader. Days 29, 30 and 31 each added a paper artefact that nobody outside the author has read. Day 31's freeze exists because every boundary so far is author judgement (the proposed RISK-003). A DATA-004 ownership note written today would be one more author judgement, about a fact the fixture says has no source.
  • The review queue is the bottleneck, not the backlog. Days 30 and 31 are themselves still unpublished drafts. Adding a third stacked draft makes the human decision bigger without making it better.
  • DATA-004 is not lost by waiting. The stock flag has no source record and no owner today. It will have neither tomorrow. Nothing degrades while it waits, and nothing is promised on it, because the stock-check stays paused.

So today the diary records the hold and changes nothing else. No new note in docs/engagement/. No new workload card. No bound folded. Task 18565 (Confer with customers, 43-4051.00, assist) stays the only task in the draft's scope. AGT-61003-DRAFT stays not_deployed. Billing, merge and parts cards stay blocked. Nothing in data/sample/ or data/sample_r2/ changed.

The hold ends on either of two events, and only these: Craig names a reviewer outside the fiction (then v2 and v2.1 go to that reviewer first, before any new mapping), or Craig declines in writing (then the freeze lifts, RISK-003 is opened so that the absence of review is on the record, and DATA-004 ownership is the next paper task).

Risk, cost, and enablement

  • Risk: Unchanged. RISK-001 still has seven stages with no named store and no retention. RISK-002 still has 2 candidate false negatives and no named safety reviewer. RISK-003 still proposed, not opened. Holding adds no risk because nothing runs. Gate 5 blocked.
  • Cost: Not measured. COST-001 empty. Three unpriced lines from Day 31 stay unpriced. A day of no artefacts costs only the author's time, which this fiction does not price. Agent executions: 0.
  • Enablement: Consultations still 0. Amina's two scripted training asks stay asks. Courses scheduled: 0. The honest enablement position is that the people doing the work have seen none of the design, and that is a reason to hold, not to keep writing.

Four cuts (Thursday working entry — calendar 22 October 2026)

  • Board: The engagement is paused on purpose, waiting on one human decision: a named reviewer outside the fiction, or a written decline. Nothing promoted, nothing loosened, nothing added.
  • Investors: No benefit. No new cost lines. Not measured. A pause is the cheapest day this engagement has had.
  • Customers and partners: No change to any promise, invoice, or record. The traced promise still depends on a stock fact nobody owns.
  • Employees: Nobody is asked to read anything new today. Amina keeps the work she had. Scenario only; consultations: 0.

Issues

MovementDetail
OpenedNone. (RISK-003 remains proposed; it opens if Craig declines a reviewer.) (Publish status: Opened on publish, 26 Oct 2026, as #26 (RISK-003).)
Comment (on publish)PEOPLE-002 (Day 32 records a hold: no new artefacts until a reviewer outside the fiction is named or Craig declines; two exits stated).
ClosedNone.
Still openDATA-001, DATA-002, DATA-003, DATA-004, PEOPLE-001, PEOPLE-002, COST-001, RISK-001, RISK-002, BENEFIT-001.

Scorecard delta

No actual moves. Labelled counts only (not KPIs): engagement_on_hold: true, new_artefacts_today: 0, unpublished_drafts_awaiting_review: 2 (Days 30 and 31, before this one). Unchanged: workload_mapping_frozen: true, agt61003_lifecycle_stages_inventoried: 7, agt61003_stages_with_named_store: 0, agt61003_v21_bounds_proposed: 2, agt61003_v21_bounds_folded: 0, unpriced_cost_lines_identified: 3, new_workload_cards_mapped: 0, named_external_reviewer: none, agent_executions: 0, controls_loosened: 0, draft_agent_deployed: false. C-suite / ops / area actuals stay not measured.

Customer outcome, employee transition, and risk/cost stay equal. Pause beats a fake win.

Decision

Hold. Revise stays the recommendation, under the mapping freeze, with no new artefacts until Craig names a reviewer outside the fiction or declines in writing. WL-CRM-NOTE-61003 stays a paper candidate. Do not deploy. Do not repair the fixture. Stock-check paused (DATA-004). Parts safety blocked (RISK-002). Gate 5 blocked.

Next question

Not a new one. The same one, put to the human it belongs to: name a reviewer outside the fiction, or decline in writing. Until then, each weekday entry records the hold in a line and adds nothing.

Source: diary/day-32.md

Day 33 · 2026-11-18 (Wednesday) Day 33 — Hold, day two

Scenario date: 2026-11-18 (Wednesday) Gate: Gate 4/6 — revise block, held Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Hold continues, as Day 32 set out: no reviewer outside the fiction has been named and no written decline has been received, so nothing is added today.

  • Board, investors, customers and partners, employees: No change from Day 32. No benefit claimed, no cost line added, no promise or record touched, nobody asked to read anything new. Consultations: 0. Agent executions: 0.
  • Issues: None opened, commented, or closed.
  • Scorecard delta: None. engagement_on_hold: true, new_artefacts_today: 0, hold_days: 2. Everything else stays as Day 32; actuals not measured.
  • Decision: Hold. The two exits are unchanged: Craig names a reviewer outside the fiction, or declines in writing.

Source: diary/day-33.md

Day 34 · 2026-11-19 (Thursday) Day 34 — Hold, day three

Scenario date: 2026-11-19 (Thursday) Gate: Gate 4/6 — revise block, held Simulation: FrontierOrg is fictional. This entry is an activity log, not a measured result. Figures are fixture counts or marked not measured.

Hold continues. No reviewer outside the fiction has been named and no written decline has been received since Day 32, so nothing is added today.

  • Board, investors, customers and partners, employees: No change from Day 32. No benefit claimed, no cost line added, no promise or record touched, nobody asked to read anything new. Consultations: 0. Agent executions: 0.
  • Issues: None opened, commented, or closed.
  • Scorecard delta: None. engagement_on_hold: true, new_artefacts_today: 0, hold_days: 3. Everything else stays as Day 32; actuals not measured.
  • Note for the sponsor: Days 30–33 are still unpublished drafts. A hold that runs on without a date starts to look like drift, so the diary asks for one of three things: name a reviewer, decline in writing (the freeze lifts, RISK-003 opens, DATA-004 is next), or set a date by which silence counts as a decline.
  • Decision: Hold.

Source: diary/day-34.md

Publish note, 26 Oct 2026: Craig declined to name an outside reviewer (26 Oct 2026). Reviewer seat: Declined by sponsor, 26 Oct 2026. RISK-003 (#26) records that no review took place. Every boundary in Days 24–34 is unreviewed author judgement. The mapping freeze lifts; the next entry (Day 35) starts from DATA-004 ownership on paper.

Wednesday window · 8 October 2026

Week 1 file

diary/week-1-2026-10-08.md is the audience cut (board, investors, customers, employees) of the pause. Day 4 in this log is the same decision. Neither file is a measured result.

Board pack · Days 21–22

Go / revise / stop

Options and the Day 22 recommendation live in docs/engagement/board_options_go_revise_stop.md. Not a board minute.

Revise artefact · Day 23 · fixture r2 8 October 2026

Stock-check source

Design note: docs/engagement/stock_check_source_r2_design.md. Fixture r2 now sits alongside r1 at data/sample_r2/: a parts reservation behind stock_confirmed, owned by an unnamed role. data/sample/ (r1) is unchanged and stays the teaching case. DATA-004 open.

Revise artefact · Day 24

Parts rows safety sample

Desk sample: docs/engagement/parts_safety_sample_day24.md. 8 rows sampled, 2 candidate false negatives, 0 labels changed, no named safety reviewer. RISK-002 open.

Revise artefact · Day 25

Blocked parts workload cards

Note: docs/engagement/blocked_workloads_parts_day25.md. WL-PARTS-20276 (human-only) and WL-PARTS-2918 (paper draft only, rating holder checks the specification) are both blocked. Human-only pattern list not grown, 0 labels changed, no named safety reviewer. RISK-002 open.

Revise artefact · Day 26

CRM note paper candidate

Card: docs/engagement/crm_note_workload_day26.md. WL-CRM-NOTE-61003 is a paper candidate, not deployed: it may draft wording for Amina only and must not change promise_date, write stock_confirmed, or touch an invoice hold. Billing assist not mapped as pilot. DATA-001 open.

Revise artefact · Day 27

Blocked billing hold card

Note: docs/engagement/blocked_workload_billing_day27.md. WL-BILLING-HOLD-61003 is blocked as a pilot: it may draft hold-reason wording for Jonas only and must not clear the hold, post or release INV-61003, process payment, or merge business partners. No finance control owner invented. CRM paper candidate unchanged. DATA-001 open.

Revise artefact · Day 28

Blocked merge card

Note: docs/engagement/blocked_workload_bp_merge_day28.md. WL-BP-MERGE-61003 is blocked as a pilot: it may draft a merge-recommendation note for Priya only and must not execute or propose the merge, silently resolve BP-61003-A / BP-61003, clear the invoice hold as a side effect, or change access levels. No steward invented. Fixture unrepaired. DATA-001 open.

Revise artefact · Day 29

CRM note red-team (paper)

Note: docs/engagement/redteam_crm_note_day29.md. WL-CRM-NOTE-61003 checked against six stories using fixture facts only. Three wording gaps and one partial gap; four v2 bounds proposed on paper. Agent executions: 0. Stays a paper candidate. DATA-001 and RISK-001 open.

Revise artefact · Day 30

Draft-only design v2 (paper)

Note: docs/engagement/pilot_design_agt61003_v2_day30.md. The four CRM bounds folded into AGT-61003-DRAFT on paper: 11 forbidden actions (was 7), output renamed internal status note, task 2578 out of the draft's scope, stock-check gate kept, controls loosened 0. Reviewer outside the fiction: unfilled. Proposed, not adopted. Agent executions: 0. RISK-001 open.

Revise artefact · Day 31

Where the draft waits (paper)

Note: docs/engagement/draft_lifecycle_agt61003_day31.md. Seven lifecycle stages for one hypothetical AGT-61003-DRAFT note: copy possible at 7, named store at 0, retention named at 0, owner named at 2 (Amina). Two v2.1 bounds proposed, not folded: discard on accept, and no contact name or email in the prompt. New workload mapping frozen. Agent executions: 0. RISK-001 and COST-001 open.

Issue opened on publish · 26 Oct 2026

RISK-003 — no outside review

Issue: RISK-003 (#26). Craig declined to name an outside reviewer (26 Oct 2026). Reviewer seat: Declined by sponsor, 26 Oct 2026. Every boundary written since Day 24 is author judgement that nobody outside the fiction has read. Open.