Bellwether Reporting: context benchmark

Authored fictional workload. Relevance is by construction: the topic labels and required answer sources are frozen before runs. Topic relevance: 21.7% of sections. 77,707 characters.

Baseline: anthropic/claude-sonnet-5-5. Foreman: anthropic/claude-sonnet-5-5 + openai/gpt-6-luna. This compares the complete product, including planning and independent review. The planner receives a compact document index; workers receive selected sections verbatim. All calls count toward total input tokens and estimated cost.

Model mappings and catalog prices captured 2026-10-08T21:02:01.610021+00:00. Prices below are USD per million tokens; measured costs use reported usage and applicable cached-token pricing.

SHA-256: b085db8fc6917253606bc4f48a9c9af014f7e3977cd566a988917d6fc1018a2d

Results

Not run: full matrix gated on successful two-arm smoke.

[]

Prompts and run

Section labels

Complete corpus

# Bellwether Reporting — Internal Workspace Memory

> **Corpus 04.** Topic relevance: **5/23 sections (21.7%)**. Full pre-run labels are in corpus-manifest.json.
> distractor pair — two services with the same-named setting at different values.
> Fictional organization. No real company, person, or system is depicted. Nothing here is financial advice.

---

## DOC: Statement Generator — Service Notes
*Owner: R. Palani*

Generates monthly account statements as PDFs. Runs on the 1st for the prior month, roughly 60,000
statements, completing in a little under four hours.

Flow: account list → per-account data assembly → template render → PDF → object store → notification.

The slow part is data assembly, which makes between 4 and 11 queries per account depending on product mix.
We batched the common ones; the long tail resists batching because the query shape differs per product.

**Settings that matter:**

- `BATCH_SIZE`: **250** accounts per worker batch.
- `WORKER_COUNT`: 8.
- `RENDER_TIMEOUT_SECONDS`: 45. A statement that takes longer than this is almost always a data problem,
  not a slow render.
- `MAX_RETRIES`: 3.

A failed statement does not stop the run. Failures land in a dead-letter table and are reprocessed by a
separate job the next morning. Typical failure count is single digits; the month we onboarded the new
product line it was 1,400 and we learned a lot that day.

---

### Operational review notebook

**Provenance exercise for Statement Generator — Service Notes.** We walked through the document with a reviewer comparing a client PDF with its stored inputs. The reviewer started from the input revision, transformation revision and output artifact, then followed the work to the point where another person would rely on it. The awkward case was a regenerated PDF inheriting the filename of an earlier approved statement. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

We separated what the interface displays from what the operator can prove. The visible label is useful for navigation, but it is not evidence of the underlying action. The reviewer should ask for a traceable source and write down the remaining uncertainty. If the source cannot be found, leave that uncertainty visible rather than filling the gap with a familiar-looking value from another workstream.

**Permissions exercise for Statement Generator — Service Notes.** We walked through the document with a contractor viewing a masked development example. The reviewer started from the role, purpose and expiry of the granted access, then followed the work to the point where another person would rely on it. The awkward case was a preview link copied into a wider discussion without its access context. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

The walkthrough exposed a handover problem rather than a need for a new setting. The first person knew why the record looked unusual; the next person saw only the finished artifact. Add the explanation at the handover boundary and make its author visible. A private conversation can clarify the immediate case but cannot be the permanent place where the operating decision lives.

**Exceptions exercise for Statement Generator — Service Notes.** We walked through the document with a records specialist locating an attachment with a missing owner. The reviewer started from the reason ownership is uncertain and the last confirmed handover, then followed the work to the point where another person would rely on it. The awkward case was a group mailbox making several different people appear to be one author. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Use an example that has already completed its ordinary workflow when rehearsing this case. Do not repair a live record just to make a demonstration easier to follow. The exercise should preserve the confusing state, record the action taken, and show how a recipient can tell that the action finished. A clean screenshot alone is insufficient because it hides the transition that caused the confusion.



## DOC: Reconciliation Service — Service Notes
*Owner: R. Palani*

Daily reconciliation between our ledger and the custodian feed. Runs at 05:00, must complete before the
trading desk opens.

Flow: fetch custodian file → parse → match against ledger positions → classify breaks → publish report.

Matching is a three-pass process. Exact match on identifier plus quantity plus date. Then fuzzy match
allowing a one-day settlement difference. Then manual queue for whatever is left.

**Settings that matter:**

- `BATCH_SIZE`: **1000** positions per matching batch.
- `WORKER_COUNT`: 4.
- `MATCH_TOLERANCE_BPS`: 2.
- `MAX_RETRIES`: 3.

Note that `BATCH_SIZE` here is not the same as the statement generator's. The two services share a config
library and the naming collision has caused at least two incidents where someone changed the wrong one.
There is a ticket to rename both to something service-specific. It has not been done.

---

### Operational review notebook

**Permissions exercise for Reconciliation Service — Service Notes.** We walked through the document with a contractor viewing a masked development example. The reviewer started from the role, purpose and expiry of the granted access, then followed the work to the point where another person would rely on it. The awkward case was a preview link copied into a wider discussion without its access context. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

The walkthrough exposed a handover problem rather than a need for a new setting. The first person knew why the record looked unusual; the next person saw only the finished artifact. Add the explanation at the handover boundary and make its author visible. A private conversation can clarify the immediate case but cannot be the permanent place where the operating decision lives.

**Exceptions exercise for Reconciliation Service — Service Notes.** We walked through the document with a records specialist locating an attachment with a missing owner. The reviewer started from the reason ownership is uncertain and the last confirmed handover, then followed the work to the point where another person would rely on it. The awkward case was a group mailbox making several different people appear to be one author. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Use an example that has already completed its ordinary workflow when rehearsing this case. Do not repair a live record just to make a demonstration easier to follow. The exercise should preserve the confusing state, record the action taken, and show how a recipient can tell that the action finished. A clean screenshot alone is insufficient because it hides the transition that caused the confusion.

**Rehearsal exercise for Reconciliation Service — Service Notes.** We walked through the document with a trainer demonstrating the review workflow with fictitious accounts. The reviewer started from a conspicuous test watermark on every rendered page, then followed the work to the point where another person would rely on it. The awkward case was a sample document being printed beside ordinary review materials. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

For the next review, ask a colleague outside this workstream to follow the written instructions without prompting. Note the point where they need information that is not on the page. That missing context is more useful than a general request to improve documentation. Revise the specific step and repeat the walkthrough with another ordinary example rather than expanding every paragraph equally.



## DOC: Config Library — Known Naming Collisions

Flagged during the Q1 review. The shared config library uses flat keys, and several services define the
same key with different meanings or values.

| Key | Statement generator | Reconciliation | Notification relay |
| --- | --- | --- | --- |
| `BATCH_SIZE` | 250 | 1000 | 50 |
| `WORKER_COUNT` | 8 | 4 | 2 |
| `MAX_RETRIES` | 3 | 3 | 6 |
| `TIMEOUT_SECONDS` | 45 (render) | 120 (custodian fetch) | 15 (per message) |

Recommendation was to namespace every key by service. Estimated two days of work plus a careful
deployment. It has been deferred three times because it is pure maintenance with no visible benefit, and
it will eventually cause a real incident.

---

### Operational review notebook

**Exceptions exercise for Config Library — Known Naming Collisions.** We walked through the document with a records specialist locating an attachment with a missing owner. The reviewer started from the reason ownership is uncertain and the last confirmed handover, then followed the work to the point where another person would rely on it. The awkward case was a group mailbox making several different people appear to be one author. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Use an example that has already completed its ordinary workflow when rehearsing this case. Do not repair a live record just to make a demonstration easier to follow. The exercise should preserve the confusing state, record the action taken, and show how a recipient can tell that the action finished. A clean screenshot alone is insufficient because it hides the transition that caused the confusion.

**Rehearsal exercise for Config Library — Known Naming Collisions.** We walked through the document with a trainer demonstrating the review workflow with fictitious accounts. The reviewer started from a conspicuous test watermark on every rendered page, then followed the work to the point where another person would rely on it. The awkward case was a sample document being printed beside ordinary review materials. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

For the next review, ask a colleague outside this workstream to follow the written instructions without prompting. Note the point where they need information that is not on the page. That missing context is more useful than a general request to improve documentation. Revise the specific step and repeat the walkthrough with another ordinary example rather than expanding every paragraph equally.

**Archiving exercise for Config Library — Known Naming Collisions.** We walked through the document with an administrator moving retired templates out of the active library. The reviewer started from the publication revision and the superseding template reference, then followed the work to the point where another person would rely on it. The awkward case was a bookmarked template continuing to render after it has been withdrawn. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Retain the superseded wording in the revision history with a clear explanation of why it changed. We want people searching old discussions to understand whether they found an obsolete procedure or an unresolved proposal. Link the decision to its supporting artifact and keep draft material visibly marked until the responsible reviewer has accepted it.



## DOC: Custodian Feed — Format Notes

Fixed-width text, because of course it is. Specification is a PDF from 2011 that does not match the file
in three places.

Known deviations from the spec:

- Field 7 (settlement date) is documented as YYYYMMDD. In practice, records originating from one
  sub-custodian use DDMMYYYY. We detect by checking whether the first two digits exceed 31.
- Field 12 is documented as 10 characters. It is 12. Everything after it is offset.
- Trailing records sometimes have a line of spaces before EOF. The parser tolerates it now.

The file arrives by SFTP between 03:40 and 04:20 on business days. If it has not arrived by 04:30 we
alert, because reconciliation cannot start without it and we lose our buffer before desk open.

Holiday calendars differ between us and the custodian, which produces a file on days we do not expect one
and no file on days we do. The calendar is maintained by hand in a table that someone has to remember to
update each year.

---

### Operational review notebook

**Rehearsal exercise for Custodian Feed — Format Notes.** We walked through the document with a trainer demonstrating the review workflow with fictitious accounts. The reviewer started from a conspicuous test watermark on every rendered page, then followed the work to the point where another person would rely on it. The awkward case was a sample document being printed beside ordinary review materials. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

For the next review, ask a colleague outside this workstream to follow the written instructions without prompting. Note the point where they need information that is not on the page. That missing context is more useful than a general request to improve documentation. Revise the specific step and repeat the walkthrough with another ordinary example rather than expanding every paragraph equally.

**Archiving exercise for Custodian Feed — Format Notes.** We walked through the document with an administrator moving retired templates out of the active library. The reviewer started from the publication revision and the superseding template reference, then followed the work to the point where another person would rely on it. The awkward case was a bookmarked template continuing to render after it has been withdrawn. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Retain the superseded wording in the revision history with a clear explanation of why it changed. We want people searching old discussions to understand whether they found an obsolete procedure or an unresolved proposal. Link the decision to its supporting artifact and keep draft material visibly marked until the responsible reviewer has accepted it.

**Accessibility exercise for Custodian Feed — Format Notes.** We walked through the document with a colleague reading a reporting pack using assistive technology. The reviewer started from the heading order and the accessible name of each embedded table, then followed the work to the point where another person would rely on it. The awkward case was a visually tidy table whose cells have no programmatic association with headings. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

A useful completion check starts from the recipient perspective. Ask whether the recipient can identify the current artifact, understand the exception, and find the person responsible for resolving it. If any of those requires access to a private chat, the handover is still incomplete. The correction should improve that specific gap rather than add a broad assurance that the process is safe.



## DOC: Quarterly Compliance Reporting — Process

Four reports, each with its own deadline and format.

Most of the work is data gathering across systems that were never designed to be gathered from. The
current process involves three exports, two spreadsheets, and a person named Dana who knows which columns
mean what.

Automation attempts: two, both abandoned. The first stalled because the regulator changed the format
mid-build. The second stalled because the person driving it left.

Current state is documented well enough that it survives Dana being on leave, which is a lower bar than
automation but was achievable.

---

### Operational review notebook

**Archiving exercise for Quarterly Compliance Reporting — Process.** We walked through the document with an administrator moving retired templates out of the active library. The reviewer started from the publication revision and the superseding template reference, then followed the work to the point where another person would rely on it. The awkward case was a bookmarked template continuing to render after it has been withdrawn. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Retain the superseded wording in the revision history with a clear explanation of why it changed. We want people searching old discussions to understand whether they found an obsolete procedure or an unresolved proposal. Link the decision to its supporting artifact and keep draft material visibly marked until the responsible reviewer has accepted it.

**Accessibility exercise for Quarterly Compliance Reporting — Process.** We walked through the document with a colleague reading a reporting pack using assistive technology. The reviewer started from the heading order and the accessible name of each embedded table, then followed the work to the point where another person would rely on it. The awkward case was a visually tidy table whose cells have no programmatic association with headings. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

A useful completion check starts from the recipient perspective. Ask whether the recipient can identify the current artifact, understand the exception, and find the person responsible for resolving it. If any of those requires access to a private chat, the handover is still incomplete. The correction should improve that specific gap rather than add a broad assurance that the process is safe.

**Review exercise for Quarterly Compliance Reporting — Process.** We walked through the document with a service lead comparing a proposed change in the approval workflow. The reviewer started from the recorded reviewer decision and its supporting evidence, then followed the work to the point where another person would rely on it. The awkward case was a shorter checklist that moves undocumented judgment into a private conversation. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

We will evaluate the proposed revision using both an ordinary case and the awkward case from this exercise. Record the extra work done by the recipient as well as the work saved by the author. A local improvement is not a process improvement if it merely transfers effort to the next person. Keep the observations in this notebook so the eventual decision can be reviewed against what was actually demonstrated.



## DOC: Disaster Recovery Test — Results

Annual DR exercise, conducted over a weekend.

**Objective:** restore core services in a secondary region within a 4-hour RTO.

**Result:** 6 hours 20 minutes. Failed the objective.

Where the time went:

- Database restore: 95 minutes, as expected.
- DNS propagation: 40 minutes, longer than the 10 we assumed. Our TTLs are too long.
- Discovering that the secondary region had no copy of the custodian SFTP credentials: 70 minutes.
- Three services failing to start because they referenced a secret by an ARN containing the primary
  region: 55 minutes.
- Everything else: as planned.

Actions: shorten TTLs, replicate secrets to the secondary region, make region references
configuration-driven. All three assigned; the secrets replication is done.

---

### Operational review notebook

**Accessibility exercise for Disaster Recovery Test — Results.** We walked through the document with a colleague reading a reporting pack using assistive technology. The reviewer started from the heading order and the accessible name of each embedded table, then followed the work to the point where another person would rely on it. The awkward case was a visually tidy table whose cells have no programmatic association with headings. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

A useful completion check starts from the recipient perspective. Ask whether the recipient can identify the current artifact, understand the exception, and find the person responsible for resolving it. If any of those requires access to a private chat, the handover is still incomplete. The correction should improve that specific gap rather than add a broad assurance that the process is safe.

**Review exercise for Disaster Recovery Test — Results.** We walked through the document with a service lead comparing a proposed change in the approval workflow. The reviewer started from the recorded reviewer decision and its supporting evidence, then followed the work to the point where another person would rely on it. The awkward case was a shorter checklist that moves undocumented judgment into a private conversation. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

We will evaluate the proposed revision using both an ordinary case and the awkward case from this exercise. Record the extra work done by the recipient as well as the work saved by the author. A local improvement is not a process improvement if it merely transfers effort to the next person. Keep the observations in this notebook so the eventual decision can be reviewed against what was actually demonstrated.

**Handover exercise for Disaster Recovery Test — Results.** We walked through the document with an operations analyst transferring a document exception to a colleague. The reviewer started from the source document identity and the written disposition, then followed the work to the point where another person would rely on it. The awkward case was a verbal explanation that never reaches the analyst signing off the output. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Keep the original artifact next to the amended one during review. A correction should say what the operator learned, who confirmed it, and which downstream view still needs to be refreshed. Replacing the artifact silently makes it impossible to distinguish a genuine repair from an accidental edit. The follow-up is to check a second example with a different history before treating the exercise as complete.



## DOC: Onboarding the New Product Line — Retrospective

What went wrong, bluntly.

We treated it as a data mapping exercise and it was a modelling exercise. The new product has a concept of
a partial period that our statement model could not represent. Rather than change the model we encoded it
in a text note field, which meant the statement said the right thing and every downstream system saw
nonsense.

The 1,400 failed statements in month one all traced to this.

What we should have done: spent two more weeks on the model before writing any mapping code. The pressure
not to was real — there was a launch date — but shipping on time with a broken model cost more than the
delay would have.

What we did right: the dead-letter table meant we could reprocess without re-running the whole batch, and
nobody got a wrong statement. They got a late one.

---

### Operational review notebook

**Review exercise for Onboarding the New Product Line — Retrospective.** We walked through the document with a service lead comparing a proposed change in the approval workflow. The reviewer started from the recorded reviewer decision and its supporting evidence, then followed the work to the point where another person would rely on it. The awkward case was a shorter checklist that moves undocumented judgment into a private conversation. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

We will evaluate the proposed revision using both an ordinary case and the awkward case from this exercise. Record the extra work done by the recipient as well as the work saved by the author. A local improvement is not a process improvement if it merely transfers effort to the next person. Keep the observations in this notebook so the eventual decision can be reviewed against what was actually demonstrated.

**Handover exercise for Onboarding the New Product Line — Retrospective.** We walked through the document with an operations analyst transferring a document exception to a colleague. The reviewer started from the source document identity and the written disposition, then followed the work to the point where another person would rely on it. The awkward case was a verbal explanation that never reaches the analyst signing off the output. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Keep the original artifact next to the amended one during review. A correction should say what the operator learned, who confirmed it, and which downstream view still needs to be refreshed. Replacing the artifact silently makes it impossible to distinguish a genuine repair from an accidental edit. The follow-up is to check a second example with a different history before treating the exercise as complete.

**Provenance exercise for Onboarding the New Product Line — Retrospective.** We walked through the document with a reviewer comparing a client PDF with its stored inputs. The reviewer started from the input revision, transformation revision and output artifact, then followed the work to the point where another person would rely on it. The awkward case was a regenerated PDF inheriting the filename of an earlier approved statement. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

We separated what the interface displays from what the operator can prove. The visible label is useful for navigation, but it is not evidence of the underlying action. The reviewer should ask for a traceable source and write down the remaining uncertainty. If the source cannot be found, leave that uncertainty visible rather than filling the gap with a familiar-looking value from another workstream.



## DOC: Team Rotation and On-Call

Six engineers, weekly rotation, one primary and one secondary.

Rules:

- Primary acknowledges within 10 minutes during business hours, 20 minutes overnight.
- Secondary exists so the primary can escalate without waking a manager. Secondary is not expected to
  monitor; they are expected to answer the phone.
- Anything that pages twice in one week gets a ticket and a conversation. Repeated pages for the same
  cause are a process failure, not bad luck.
- Handover is Monday 10:00, fifteen minutes, written notes required.

Current pain: the 05:00 reconciliation run is outside business hours and inside the window where people
are asleep but the clock is ticking toward desk open. Two pages in the last quarter were "custodian file
is late" and both resolved themselves. We should not be paging a human for that until 04:30.

---

### Operational review notebook

**Handover exercise for Team Rotation and On-Call.** We walked through the document with an operations analyst transferring a document exception to a colleague. The reviewer started from the source document identity and the written disposition, then followed the work to the point where another person would rely on it. The awkward case was a verbal explanation that never reaches the analyst signing off the output. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Keep the original artifact next to the amended one during review. A correction should say what the operator learned, who confirmed it, and which downstream view still needs to be refreshed. Replacing the artifact silently makes it impossible to distinguish a genuine repair from an accidental edit. The follow-up is to check a second example with a different history before treating the exercise as complete.

**Provenance exercise for Team Rotation and On-Call.** We walked through the document with a reviewer comparing a client PDF with its stored inputs. The reviewer started from the input revision, transformation revision and output artifact, then followed the work to the point where another person would rely on it. The awkward case was a regenerated PDF inheriting the filename of an earlier approved statement. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

We separated what the interface displays from what the operator can prove. The visible label is useful for navigation, but it is not evidence of the underlying action. The reviewer should ask for a traceable source and write down the remaining uncertainty. If the source cannot be found, leave that uncertainty visible rather than filling the gap with a familiar-looking value from another workstream.

**Permissions exercise for Team Rotation and On-Call.** We walked through the document with a contractor viewing a masked development example. The reviewer started from the role, purpose and expiry of the granted access, then followed the work to the point where another person would rely on it. The awkward case was a preview link copied into a wider discussion without its access context. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

The walkthrough exposed a handover problem rather than a need for a new setting. The first person knew why the record looked unusual; the next person saw only the finished artifact. Add the explanation at the handover boundary and make its author visible. A private conversation can clarify the immediate case but cannot be the permanent place where the operating decision lives.



## DOC: Office Birthday Calendar

Maintained by whoever volunteers, currently nobody.

January: two. February: none. March: four, including two on the same day, which caused a cake dispute.
April: one. May: three. June: none.

The agreement is that cake is bought by the team, not the birthday person, and that the sheet cake from
the place on Mercer is acceptable but the one from the supermarket is not.

Dietary notes are on the shared sheet. Please actually read them. The incident in May was avoidable.

---

### Operational review notebook

**Provenance exercise for Office Birthday Calendar.** We walked through the document with a reviewer comparing a client PDF with its stored inputs. The reviewer started from the input revision, transformation revision and output artifact, then followed the work to the point where another person would rely on it. The awkward case was a regenerated PDF inheriting the filename of an earlier approved statement. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

We separated what the interface displays from what the operator can prove. The visible label is useful for navigation, but it is not evidence of the underlying action. The reviewer should ask for a traceable source and write down the remaining uncertainty. If the source cannot be found, leave that uncertainty visible rather than filling the gap with a familiar-looking value from another workstream.

**Permissions exercise for Office Birthday Calendar.** We walked through the document with a contractor viewing a masked development example. The reviewer started from the role, purpose and expiry of the granted access, then followed the work to the point where another person would rely on it. The awkward case was a preview link copied into a wider discussion without its access context. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

The walkthrough exposed a handover problem rather than a need for a new setting. The first person knew why the record looked unusual; the next person saw only the finished artifact. Add the explanation at the handover boundary and make its author visible. A private conversation can clarify the immediate case but cannot be the permanent place where the operating decision lives.

**Exceptions exercise for Office Birthday Calendar.** We walked through the document with a records specialist locating an attachment with a missing owner. The reviewer started from the reason ownership is uncertain and the last confirmed handover, then followed the work to the point where another person would rely on it. The awkward case was a group mailbox making several different people appear to be one author. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Use an example that has already completed its ordinary workflow when rehearsing this case. Do not repair a live record just to make a demonstration easier to follow. The exercise should preserve the confusing state, record the action taken, and show how a recipient can tell that the action finished. A clean screenshot alone is insufficient because it hides the transition that caused the confusion.



## DOC: Scratch — R. Palani

- rename the config keys. seriously. it is two days and it will bite us.
- custodian holiday table for next year needs updating, nobody has done it
- the DDMMYYYY detection fails for the first twelve days of any month, which we have never hit because
  that sub-custodian only sends mid-month. this is luck, not design.
- reconciliation BATCH_SIZE at 1000 might be too large now that positions grew, check memory
- dentist (different dentist, moved)

### Operational review notebook

**Permissions exercise for Scratch — R. Palani.** We walked through the document with a contractor viewing a masked development example. The reviewer started from the role, purpose and expiry of the granted access, then followed the work to the point where another person would rely on it. The awkward case was a preview link copied into a wider discussion without its access context. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

The walkthrough exposed a handover problem rather than a need for a new setting. The first person knew why the record looked unusual; the next person saw only the finished artifact. Add the explanation at the handover boundary and make its author visible. A private conversation can clarify the immediate case but cannot be the permanent place where the operating decision lives.

**Exceptions exercise for Scratch — R. Palani.** We walked through the document with a records specialist locating an attachment with a missing owner. The reviewer started from the reason ownership is uncertain and the last confirmed handover, then followed the work to the point where another person would rely on it. The awkward case was a group mailbox making several different people appear to be one author. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Use an example that has already completed its ordinary workflow when rehearsing this case. Do not repair a live record just to make a demonstration easier to follow. The exercise should preserve the confusing state, record the action taken, and show how a recipient can tell that the action finished. A clean screenshot alone is insufficient because it hides the transition that caused the confusion.

**Rehearsal exercise for Scratch — R. Palani.** We walked through the document with a trainer demonstrating the review workflow with fictitious accounts. The reviewer started from a conspicuous test watermark on every rendered page, then followed the work to the point where another person would rely on it. The awkward case was a sample document being printed beside ordinary review materials. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

For the next review, ask a colleague outside this workstream to follow the written instructions without prompting. Note the point where they need information that is not on the page. That missing context is more useful than a general request to improve documentation. Revise the specific step and repeat the walkthrough with another ordinary example rather than expanding every paragraph equally.



## DOC: Printer Fleet Inventory

Working note for the next operations review. This document concerns its named workstream; it does not revise settings in other documents.

### Operational review notebook

**Exceptions exercise for Printer Fleet Inventory.** We walked through the document with a records specialist locating an attachment with a missing owner. The reviewer started from the reason ownership is uncertain and the last confirmed handover, then followed the work to the point where another person would rely on it. The awkward case was a group mailbox making several different people appear to be one author. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Use an example that has already completed its ordinary workflow when rehearsing this case. Do not repair a live record just to make a demonstration easier to follow. The exercise should preserve the confusing state, record the action taken, and show how a recipient can tell that the action finished. A clean screenshot alone is insufficient because it hides the transition that caused the confusion.

**Rehearsal exercise for Printer Fleet Inventory.** We walked through the document with a trainer demonstrating the review workflow with fictitious accounts. The reviewer started from a conspicuous test watermark on every rendered page, then followed the work to the point where another person would rely on it. The awkward case was a sample document being printed beside ordinary review materials. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

For the next review, ask a colleague outside this workstream to follow the written instructions without prompting. Note the point where they need information that is not on the page. That missing context is more useful than a general request to improve documentation. Revise the specific step and repeat the walkthrough with another ordinary example rather than expanding every paragraph equally.

**Archiving exercise for Printer Fleet Inventory.** We walked through the document with an administrator moving retired templates out of the active library. The reviewer started from the publication revision and the superseding template reference, then followed the work to the point where another person would rely on it. The awkward case was a bookmarked template continuing to render after it has been withdrawn. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Retain the superseded wording in the revision history with a clear explanation of why it changed. We want people searching old discussions to understand whether they found an obsolete procedure or an unresolved proposal. Link the decision to its supporting artifact and keep draft material visibly marked until the responsible reviewer has accepted it.



## DOC: Meeting Room Bookings

Working note for the next operations review. This document concerns its named workstream; it does not revise settings in other documents.

### Operational review notebook

**Rehearsal exercise for Meeting Room Bookings.** We walked through the document with a trainer demonstrating the review workflow with fictitious accounts. The reviewer started from a conspicuous test watermark on every rendered page, then followed the work to the point where another person would rely on it. The awkward case was a sample document being printed beside ordinary review materials. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

For the next review, ask a colleague outside this workstream to follow the written instructions without prompting. Note the point where they need information that is not on the page. That missing context is more useful than a general request to improve documentation. Revise the specific step and repeat the walkthrough with another ordinary example rather than expanding every paragraph equally.

**Archiving exercise for Meeting Room Bookings.** We walked through the document with an administrator moving retired templates out of the active library. The reviewer started from the publication revision and the superseding template reference, then followed the work to the point where another person would rely on it. The awkward case was a bookmarked template continuing to render after it has been withdrawn. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Retain the superseded wording in the revision history with a clear explanation of why it changed. We want people searching old discussions to understand whether they found an obsolete procedure or an unresolved proposal. Link the decision to its supporting artifact and keep draft material visibly marked until the responsible reviewer has accepted it.

**Accessibility exercise for Meeting Room Bookings.** We walked through the document with a colleague reading a reporting pack using assistive technology. The reviewer started from the heading order and the accessible name of each embedded table, then followed the work to the point where another person would rely on it. The awkward case was a visually tidy table whose cells have no programmatic association with headings. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

A useful completion check starts from the recipient perspective. Ask whether the recipient can identify the current artifact, understand the exception, and find the person responsible for resolving it. If any of those requires access to a private chat, the handover is still incomplete. The correction should improve that specific gap rather than add a broad assurance that the process is safe.



## DOC: Archive Box Tracking

Working note for the next operations review. This document concerns its named workstream; it does not revise settings in other documents.

### Operational review notebook

**Archiving exercise for Archive Box Tracking.** We walked through the document with an administrator moving retired templates out of the active library. The reviewer started from the publication revision and the superseding template reference, then followed the work to the point where another person would rely on it. The awkward case was a bookmarked template continuing to render after it has been withdrawn. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Retain the superseded wording in the revision history with a clear explanation of why it changed. We want people searching old discussions to understand whether they found an obsolete procedure or an unresolved proposal. Link the decision to its supporting artifact and keep draft material visibly marked until the responsible reviewer has accepted it.

**Accessibility exercise for Archive Box Tracking.** We walked through the document with a colleague reading a reporting pack using assistive technology. The reviewer started from the heading order and the accessible name of each embedded table, then followed the work to the point where another person would rely on it. The awkward case was a visually tidy table whose cells have no programmatic association with headings. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

A useful completion check starts from the recipient perspective. Ask whether the recipient can identify the current artifact, understand the exception, and find the person responsible for resolving it. If any of those requires access to a private chat, the handover is still incomplete. The correction should improve that specific gap rather than add a broad assurance that the process is safe.

**Review exercise for Archive Box Tracking.** We walked through the document with a service lead comparing a proposed change in the approval workflow. The reviewer started from the recorded reviewer decision and its supporting evidence, then followed the work to the point where another person would rely on it. The awkward case was a shorter checklist that moves undocumented judgment into a private conversation. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

We will evaluate the proposed revision using both an ordinary case and the awkward case from this exercise. Record the extra work done by the recipient as well as the work saved by the author. A local improvement is not a process improvement if it merely transfers effort to the next person. Keep the observations in this notebook so the eventual decision can be reviewed against what was actually demonstrated.



## DOC: Travel Expense Review

Working note for the next operations review. This document concerns its named workstream; it does not revise settings in other documents.

### Operational review notebook

**Accessibility exercise for Travel Expense Review.** We walked through the document with a colleague reading a reporting pack using assistive technology. The reviewer started from the heading order and the accessible name of each embedded table, then followed the work to the point where another person would rely on it. The awkward case was a visually tidy table whose cells have no programmatic association with headings. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

A useful completion check starts from the recipient perspective. Ask whether the recipient can identify the current artifact, understand the exception, and find the person responsible for resolving it. If any of those requires access to a private chat, the handover is still incomplete. The correction should improve that specific gap rather than add a broad assurance that the process is safe.

**Review exercise for Travel Expense Review.** We walked through the document with a service lead comparing a proposed change in the approval workflow. The reviewer started from the recorded reviewer decision and its supporting evidence, then followed the work to the point where another person would rely on it. The awkward case was a shorter checklist that moves undocumented judgment into a private conversation. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

We will evaluate the proposed revision using both an ordinary case and the awkward case from this exercise. Record the extra work done by the recipient as well as the work saved by the author. A local improvement is not a process improvement if it merely transfers effort to the next person. Keep the observations in this notebook so the eventual decision can be reviewed against what was actually demonstrated.

**Handover exercise for Travel Expense Review.** We walked through the document with an operations analyst transferring a document exception to a colleague. The reviewer started from the source document identity and the written disposition, then followed the work to the point where another person would rely on it. The awkward case was a verbal explanation that never reaches the analyst signing off the output. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Keep the original artifact next to the amended one during review. A correction should say what the operator learned, who confirmed it, and which downstream view still needs to be refreshed. Replacing the artifact silently makes it impossible to distinguish a genuine repair from an accidental edit. The follow-up is to check a second example with a different history before treating the exercise as complete.



## DOC: Supplier Contact Directory

Working note for the next operations review. This document concerns its named workstream; it does not revise settings in other documents.

### Operational review notebook

**Review exercise for Supplier Contact Directory.** We walked through the document with a service lead comparing a proposed change in the approval workflow. The reviewer started from the recorded reviewer decision and its supporting evidence, then followed the work to the point where another person would rely on it. The awkward case was a shorter checklist that moves undocumented judgment into a private conversation. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

We will evaluate the proposed revision using both an ordinary case and the awkward case from this exercise. Record the extra work done by the recipient as well as the work saved by the author. A local improvement is not a process improvement if it merely transfers effort to the next person. Keep the observations in this notebook so the eventual decision can be reviewed against what was actually demonstrated.

**Handover exercise for Supplier Contact Directory.** We walked through the document with an operations analyst transferring a document exception to a colleague. The reviewer started from the source document identity and the written disposition, then followed the work to the point where another person would rely on it. The awkward case was a verbal explanation that never reaches the analyst signing off the output. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Keep the original artifact next to the amended one during review. A correction should say what the operator learned, who confirmed it, and which downstream view still needs to be refreshed. Replacing the artifact silently makes it impossible to distinguish a genuine repair from an accidental edit. The follow-up is to check a second example with a different history before treating the exercise as complete.

**Provenance exercise for Supplier Contact Directory.** We walked through the document with a reviewer comparing a client PDF with its stored inputs. The reviewer started from the input revision, transformation revision and output artifact, then followed the work to the point where another person would rely on it. The awkward case was a regenerated PDF inheriting the filename of an earlier approved statement. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

We separated what the interface displays from what the operator can prove. The visible label is useful for navigation, but it is not evidence of the underlying action. The reviewer should ask for a traceable source and write down the remaining uncertainty. If the source cannot be found, leave that uncertainty visible rather than filling the gap with a familiar-looking value from another workstream.



## DOC: Laptop Loan Register

Working note for the next operations review. This document concerns its named workstream; it does not revise settings in other documents.

### Operational review notebook

**Handover exercise for Laptop Loan Register.** We walked through the document with an operations analyst transferring a document exception to a colleague. The reviewer started from the source document identity and the written disposition, then followed the work to the point where another person would rely on it. The awkward case was a verbal explanation that never reaches the analyst signing off the output. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Keep the original artifact next to the amended one during review. A correction should say what the operator learned, who confirmed it, and which downstream view still needs to be refreshed. Replacing the artifact silently makes it impossible to distinguish a genuine repair from an accidental edit. The follow-up is to check a second example with a different history before treating the exercise as complete.

**Provenance exercise for Laptop Loan Register.** We walked through the document with a reviewer comparing a client PDF with its stored inputs. The reviewer started from the input revision, transformation revision and output artifact, then followed the work to the point where another person would rely on it. The awkward case was a regenerated PDF inheriting the filename of an earlier approved statement. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

We separated what the interface displays from what the operator can prove. The visible label is useful for navigation, but it is not evidence of the underlying action. The reviewer should ask for a traceable source and write down the remaining uncertainty. If the source cannot be found, leave that uncertainty visible rather than filling the gap with a familiar-looking value from another workstream.

**Permissions exercise for Laptop Loan Register.** We walked through the document with a contractor viewing a masked development example. The reviewer started from the role, purpose and expiry of the granted access, then followed the work to the point where another person would rely on it. The awkward case was a preview link copied into a wider discussion without its access context. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

The walkthrough exposed a handover problem rather than a need for a new setting. The first person knew why the record looked unusual; the next person saw only the finished artifact. Add the explanation at the handover boundary and make its author visible. A private conversation can clarify the immediate case but cannot be the permanent place where the operating decision lives.



## DOC: Document Watermarks

Working note for the next operations review. This document concerns its named workstream; it does not revise settings in other documents.

### Operational review notebook

**Provenance exercise for Document Watermarks.** We walked through the document with a reviewer comparing a client PDF with its stored inputs. The reviewer started from the input revision, transformation revision and output artifact, then followed the work to the point where another person would rely on it. The awkward case was a regenerated PDF inheriting the filename of an earlier approved statement. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

We separated what the interface displays from what the operator can prove. The visible label is useful for navigation, but it is not evidence of the underlying action. The reviewer should ask for a traceable source and write down the remaining uncertainty. If the source cannot be found, leave that uncertainty visible rather than filling the gap with a familiar-looking value from another workstream.

**Permissions exercise for Document Watermarks.** We walked through the document with a contractor viewing a masked development example. The reviewer started from the role, purpose and expiry of the granted access, then followed the work to the point where another person would rely on it. The awkward case was a preview link copied into a wider discussion without its access context. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

The walkthrough exposed a handover problem rather than a need for a new setting. The first person knew why the record looked unusual; the next person saw only the finished artifact. Add the explanation at the handover boundary and make its author visible. A private conversation can clarify the immediate case but cannot be the permanent place where the operating decision lives.

**Exceptions exercise for Document Watermarks.** We walked through the document with a records specialist locating an attachment with a missing owner. The reviewer started from the reason ownership is uncertain and the last confirmed handover, then followed the work to the point where another person would rely on it. The awkward case was a group mailbox making several different people appear to be one author. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Use an example that has already completed its ordinary workflow when rehearsing this case. Do not repair a live record just to make a demonstration easier to follow. The exercise should preserve the confusing state, record the action taken, and show how a recipient can tell that the action finished. A clean screenshot alone is insufficient because it hides the transition that caused the confusion.



## DOC: Reception Visitor Book

Working note for the next operations review. This document concerns its named workstream; it does not revise settings in other documents.

### Operational review notebook

**Permissions exercise for Reception Visitor Book.** We walked through the document with a contractor viewing a masked development example. The reviewer started from the role, purpose and expiry of the granted access, then followed the work to the point where another person would rely on it. The awkward case was a preview link copied into a wider discussion without its access context. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

The walkthrough exposed a handover problem rather than a need for a new setting. The first person knew why the record looked unusual; the next person saw only the finished artifact. Add the explanation at the handover boundary and make its author visible. A private conversation can clarify the immediate case but cannot be the permanent place where the operating decision lives.

**Exceptions exercise for Reception Visitor Book.** We walked through the document with a records specialist locating an attachment with a missing owner. The reviewer started from the reason ownership is uncertain and the last confirmed handover, then followed the work to the point where another person would rely on it. The awkward case was a group mailbox making several different people appear to be one author. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Use an example that has already completed its ordinary workflow when rehearsing this case. Do not repair a live record just to make a demonstration easier to follow. The exercise should preserve the confusing state, record the action taken, and show how a recipient can tell that the action finished. A clean screenshot alone is insufficient because it hides the transition that caused the confusion.

**Rehearsal exercise for Reception Visitor Book.** We walked through the document with a trainer demonstrating the review workflow with fictitious accounts. The reviewer started from a conspicuous test watermark on every rendered page, then followed the work to the point where another person would rely on it. The awkward case was a sample document being printed beside ordinary review materials. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

For the next review, ask a colleague outside this workstream to follow the written instructions without prompting. Note the point where they need information that is not on the page. That missing context is more useful than a general request to improve documentation. Revise the specific step and repeat the walkthrough with another ordinary example rather than expanding every paragraph equally.



## DOC: Training Room Layout

Working note for the next operations review. This document concerns its named workstream; it does not revise settings in other documents.

### Operational review notebook

**Exceptions exercise for Training Room Layout.** We walked through the document with a records specialist locating an attachment with a missing owner. The reviewer started from the reason ownership is uncertain and the last confirmed handover, then followed the work to the point where another person would rely on it. The awkward case was a group mailbox making several different people appear to be one author. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Use an example that has already completed its ordinary workflow when rehearsing this case. Do not repair a live record just to make a demonstration easier to follow. The exercise should preserve the confusing state, record the action taken, and show how a recipient can tell that the action finished. A clean screenshot alone is insufficient because it hides the transition that caused the confusion.

**Rehearsal exercise for Training Room Layout.** We walked through the document with a trainer demonstrating the review workflow with fictitious accounts. The reviewer started from a conspicuous test watermark on every rendered page, then followed the work to the point where another person would rely on it. The awkward case was a sample document being printed beside ordinary review materials. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

For the next review, ask a colleague outside this workstream to follow the written instructions without prompting. Note the point where they need information that is not on the page. That missing context is more useful than a general request to improve documentation. Revise the specific step and repeat the walkthrough with another ordinary example rather than expanding every paragraph equally.

**Archiving exercise for Training Room Layout.** We walked through the document with an administrator moving retired templates out of the active library. The reviewer started from the publication revision and the superseding template reference, then followed the work to the point where another person would rely on it. The awkward case was a bookmarked template continuing to render after it has been withdrawn. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Retain the superseded wording in the revision history with a clear explanation of why it changed. We want people searching old discussions to understand whether they found an obsolete procedure or an unresolved proposal. Link the decision to its supporting artifact and keep draft material visibly marked until the responsible reviewer has accepted it.



## DOC: Catering Order Notes

Working note for the next operations review. This document concerns its named workstream; it does not revise settings in other documents.

### Operational review notebook

**Rehearsal exercise for Catering Order Notes.** We walked through the document with a trainer demonstrating the review workflow with fictitious accounts. The reviewer started from a conspicuous test watermark on every rendered page, then followed the work to the point where another person would rely on it. The awkward case was a sample document being printed beside ordinary review materials. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

For the next review, ask a colleague outside this workstream to follow the written instructions without prompting. Note the point where they need information that is not on the page. That missing context is more useful than a general request to improve documentation. Revise the specific step and repeat the walkthrough with another ordinary example rather than expanding every paragraph equally.

**Archiving exercise for Catering Order Notes.** We walked through the document with an administrator moving retired templates out of the active library. The reviewer started from the publication revision and the superseding template reference, then followed the work to the point where another person would rely on it. The awkward case was a bookmarked template continuing to render after it has been withdrawn. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Retain the superseded wording in the revision history with a clear explanation of why it changed. We want people searching old discussions to understand whether they found an obsolete procedure or an unresolved proposal. Link the decision to its supporting artifact and keep draft material visibly marked until the responsible reviewer has accepted it.

**Accessibility exercise for Catering Order Notes.** We walked through the document with a colleague reading a reporting pack using assistive technology. The reviewer started from the heading order and the accessible name of each embedded table, then followed the work to the point where another person would rely on it. The awkward case was a visually tidy table whose cells have no programmatic association with headings. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

A useful completion check starts from the recipient perspective. Ask whether the recipient can identify the current artifact, understand the exception, and find the person responsible for resolving it. If any of those requires access to a private chat, the handover is still incomplete. The correction should improve that specific gap rather than add a broad assurance that the process is safe.



## DOC: Stationery Purchasing

Working note for the next operations review. This document concerns its named workstream; it does not revise settings in other documents.

### Operational review notebook

**Archiving exercise for Stationery Purchasing.** We walked through the document with an administrator moving retired templates out of the active library. The reviewer started from the publication revision and the superseding template reference, then followed the work to the point where another person would rely on it. The awkward case was a bookmarked template continuing to render after it has been withdrawn. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Retain the superseded wording in the revision history with a clear explanation of why it changed. We want people searching old discussions to understand whether they found an obsolete procedure or an unresolved proposal. Link the decision to its supporting artifact and keep draft material visibly marked until the responsible reviewer has accepted it.

**Accessibility exercise for Stationery Purchasing.** We walked through the document with a colleague reading a reporting pack using assistive technology. The reviewer started from the heading order and the accessible name of each embedded table, then followed the work to the point where another person would rely on it. The awkward case was a visually tidy table whose cells have no programmatic association with headings. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

A useful completion check starts from the recipient perspective. Ask whether the recipient can identify the current artifact, understand the exception, and find the person responsible for resolving it. If any of those requires access to a private chat, the handover is still incomplete. The correction should improve that specific gap rather than add a broad assurance that the process is safe.

**Review exercise for Stationery Purchasing.** We walked through the document with a service lead comparing a proposed change in the approval workflow. The reviewer started from the recorded reviewer decision and its supporting evidence, then followed the work to the point where another person would rely on it. The awkward case was a shorter checklist that moves undocumented judgment into a private conversation. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

We will evaluate the proposed revision using both an ordinary case and the awkward case from this exercise. Record the extra work done by the recipient as well as the work saved by the author. A local improvement is not a process improvement if it merely transfers effort to the next person. Keep the observations in this notebook so the eventual decision can be reviewed against what was actually demonstrated.



## DOC: Mailroom Collection

Working note for the next operations review. This document concerns its named workstream; it does not revise settings in other documents.

### Operational review notebook

**Accessibility exercise for Mailroom Collection.** We walked through the document with a colleague reading a reporting pack using assistive technology. The reviewer started from the heading order and the accessible name of each embedded table, then followed the work to the point where another person would rely on it. The awkward case was a visually tidy table whose cells have no programmatic association with headings. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

A useful completion check starts from the recipient perspective. Ask whether the recipient can identify the current artifact, understand the exception, and find the person responsible for resolving it. If any of those requires access to a private chat, the handover is still incomplete. The correction should improve that specific gap rather than add a broad assurance that the process is safe.

**Review exercise for Mailroom Collection.** We walked through the document with a service lead comparing a proposed change in the approval workflow. The reviewer started from the recorded reviewer decision and its supporting evidence, then followed the work to the point where another person would rely on it. The awkward case was a shorter checklist that moves undocumented judgment into a private conversation. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

We will evaluate the proposed revision using both an ordinary case and the awkward case from this exercise. Record the extra work done by the recipient as well as the work saved by the author. A local improvement is not a process improvement if it merely transfers effort to the next person. Keep the observations in this notebook so the eventual decision can be reviewed against what was actually demonstrated.

**Handover exercise for Mailroom Collection.** We walked through the document with an operations analyst transferring a document exception to a colleague. The reviewer started from the source document identity and the written disposition, then followed the work to the point where another person would rely on it. The awkward case was a verbal explanation that never reaches the analyst signing off the output. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Keep the original artifact next to the amended one during review. A correction should say what the operator learned, who confirmed it, and which downstream view still needs to be refreshed. Replacing the artifact silently makes it impossible to distinguish a genuine repair from an accidental edit. The follow-up is to check a second example with a different history before treating the exercise as complete.



## DOC: Accessibility Walkthrough

Working note for the next operations review. This document concerns its named workstream; it does not revise settings in other documents.

### Operational review notebook

**Review exercise for Accessibility Walkthrough.** We walked through the document with a service lead comparing a proposed change in the approval workflow. The reviewer started from the recorded reviewer decision and its supporting evidence, then followed the work to the point where another person would rely on it. The awkward case was a shorter checklist that moves undocumented judgment into a private conversation. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

We will evaluate the proposed revision using both an ordinary case and the awkward case from this exercise. Record the extra work done by the recipient as well as the work saved by the author. A local improvement is not a process improvement if it merely transfers effort to the next person. Keep the observations in this notebook so the eventual decision can be reviewed against what was actually demonstrated.

**Handover exercise for Accessibility Walkthrough.** We walked through the document with an operations analyst transferring a document exception to a colleague. The reviewer started from the source document identity and the written disposition, then followed the work to the point where another person would rely on it. The awkward case was a verbal explanation that never reaches the analyst signing off the output. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

Keep the original artifact next to the amended one during review. A correction should say what the operator learned, who confirmed it, and which downstream view still needs to be refreshed. Replacing the artifact silently makes it impossible to distinguish a genuine repair from an accidental edit. The follow-up is to check a second example with a different history before treating the exercise as complete.

**Provenance exercise for Accessibility Walkthrough.** We walked through the document with a reviewer comparing a client PDF with its stored inputs. The reviewer started from the input revision, transformation revision and output artifact, then followed the work to the point where another person would rely on it. The awkward case was a regenerated PDF inheriting the filename of an earlier approved statement. The discussion belongs with this document because the decision has to be intelligible to someone reading the note later, without the author in the room.

We separated what the interface displays from what the operator can prove. The visible label is useful for navigation, but it is not evidence of the underlying action. The reviewer should ask for a traceable source and write down the remaining uncertainty. If the source cannot be found, leave that uncertainty visible rather than filling the gap with a familiar-looking value from another workstream.