# AGM080 complete fictional source packet and filled agenda

Prepared September 5, 2026 as original OpenMax editorial teaching material. This packet contains no customer data, real employee record, observed meeting result or measured OpenMax run. All people are fictional roles, every timestamp is UTC and all evidence below is reproduced in full. The case tests whether a proposed agenda can preserve authority, access, topic disposition and a 35-minute budget; it does not test whether the meeting later succeeds.

## Stable role and state keys

Roles: `MeetingOwner` = operations manager and facilitator; `ProductDecisionOwner` = product manager authorized only for the internal label choice; `EscalationDecisionOwner` = support director authorized only for the internal escalation route; `SupportEvidenceOwner` = support operations lead and evidence contributor; `UXEvidenceOwner` = author of the label-options memo, not a required attendee; `FinanceDecisionOwner` = finance manager required for a vendor-spend decision; `SupplierCoordinator` = external participant proposed only for the vendor topic.

Disposition states: `LIVE_DECISION`, `ASYNC_UPDATE`, `DEFER_NOT_READY`, and `MERGED_DUPLICATE`. Readiness states: `READY`, `CONDITIONAL`, and `NOT_READY`. These are local case keys, not universal meeting standards.

## S01 — meeting contract v1

Meeting ID `AGM080`; planned occurrence `2026-09-08T14:00:00Z` to `14:35:00Z`; internal support-routing pilot; one occurrence only. The meeting has two permitted outputs: choose one internal review-label phrase and choose an internal after-hours escalation route for the pilot. It cannot approve external rollout, supplier spend, personnel evaluation or a baseline change.

Candidate intake closed `2026-09-04T12:00:00Z`. That is both the agenda status cutoff and knowledge cutoff. `MeetingOwner` prepares draft v0.9 at 13:00, resolves access exceptions, and submits v1.0 to both decision owners. `ProductDecisionOwner` and `EscalationDecisionOwner` confirm only their own question, authority and evidence by `15:00`. `MeetingOwner` releases one accessible agenda by `16:00`. A confirmation means the agenda is suitable for discussion; it is not the decision itself.

Admission rule AR1 requires: a bounded question, named output, authorized owner, available evidence, necessary participants, synchronous value, feasible time and a stop/fallback rule. An item may be narrowed. Informational items go asynchronous. Missing authority or evidence means defer. A duplicate is merged without counting twice. Late changes require `MeetingOwner` approval, a reason, new version and an explicit statement of which time allocation changes.

## S02 — six submitted requests

The six submissions total 70 requested minutes. A06 repeats A01, so the distinct-topic demand is 63 minutes. Requested minutes describe submissions, not validated duration and not savings.

| Request | Submitted question or purpose | Requester | Requested minutes | Claimed output | Authority/evidence at cutoff | Disposition and reason |
| --- | --- | --- | ---: | --- | --- | --- |
| A01 | Choose the internal queue label: “Specialist review” or “Manual review” | `UXEvidenceOwner` | 18 | One approved pilot label | `ProductDecisionOwner`; E01 and E02 current | `LIVE_DECISION`, narrowed to the exact phrase; 12 minutes |
| A02 | Decide who receives an after-hours escalation when the specialist queue is unstaffed | `SupportEvidenceOwner` | 15 | One route and fallback owner | `EscalationDecisionOwner`; E03 and E04 current | `LIVE_DECISION`, root-cause discussion removed; 10 minutes |
| A03 | Approve a USD 4,800 supplier configuration option | `SupplierCoordinator` | 12 | Spend approval | `FinanceDecisionOwner` unavailable; E05 lacks finance review | `DEFER_NOT_READY`; do not discuss toward apparent approval |
| A04 | Review last week's pilot volumes | `SupportEvidenceOwner` | 10 | Awareness only | E06 current; no decision requested | `ASYNC_UPDATE`; one-page update by September 4, 16:00 |
| A05 | Collect wording comments on the draft operator FAQ | `MeetingOwner` | 8 | Comments | E07 accessible; comments can be written | `ASYNC_UPDATE`; comments due September 8, 12:00 |
| A06 | Pick the wording for tickets needing a specialist | `ProductDecisionOwner` | 7 | Same output as A01 | Same authority and evidence as A01 | `MERGED_DUPLICATE` into A01; preserve A06 provenance |

Arithmetic: 18 + 15 + 12 + 10 + 8 + 7 = 70 submitted minutes. A06 duplicates A01, so unique-topic demand is 70 − 7 = 63 minutes. Neither number is the meeting agenda. The two original live requests total 33 minutes, but their bounded decision segments total 22 minutes after removing background and root-cause work. The 11-minute difference is scope design, not observed efficiency and not an AI performance result.

## S03 — authority and attendance map

| Role | Authority in AGM080 | Evidence contribution | Attendance decision | Reason |
| --- | --- | --- | --- | --- |
| `MeetingOwner` | Approves agenda and facilitation changes; no authority for A01/A02 outcomes | S01 contract, timing and readback | Required | Facilitates, enforces stop rules and records provisional outcomes |
| `ProductDecisionOwner` | Decides A01 only | Confirms option boundary and decision method | Required | Named decision owner for the first live item |
| `EscalationDecisionOwner` | Decides A02 only | Confirms route ownership and exceptions | Required | Named decision owner for the second live item |
| `SupportEvidenceOwner` | No final decision authority | E03, E04 and E06 | Required | Answers operational evidence questions for A02 |
| `UXEvidenceOwner` | No decision authority | E01 and E02; available asynchronously until 13:30 | Not required | Complete memo is available; live contribution not required for the bounded choice |
| `FinanceDecisionOwner` | Required to approve A03 spend | Finance basis and spend authority absent | Not invited to this occurrence | Unavailable; A03 is deferred, not delegated |
| `SupplierCoordinator` | Can clarify supplier offer; cannot approve company spend | E05 offer | Not invited | Only proposed A03 needs this external role and A03 is not admitted |

Attendance is not authority. Four internal attendees are invited. Excluding the two evidence providers and external coordinator is a scope decision, not a claim that their work is unimportant.

## S04 — complete evidence register

All records were confirmed unchanged at the knowledge cutoff unless a different state is shown.

| Evidence | Full relevant content | Owner/version/time | Access and use |
| --- | --- | --- | --- |
| E01 | Approved pilot vocabulary permits either “Specialist review” or “Manual review”; prohibits “Rejected,” “Unsafe,” and customer-facing use. | `ProductDecisionOwner`, v3, approved September 4, 10:00 | Internal; supports A01 boundary only |
| E02 | Six fictional internal reviewers saw both phrases in the same queue mock-up. Five selected the intended meaning for “Specialist review”; three did so for “Manual review.” Free-text concerns: “specialist” does not name a team; “manual” may imply every other route is automatic. | `UXEvidenceOwner`, v1, September 4, 10:30 | Sanitized fictional review record; descriptive 5/6 and 3/6 counts, not research or customer evidence |
| E03 | Current pilot responsibility map: weekday queue owner = SupportOperations; after-hours first receiver = ServiceDesk; specialist assessment owner = SpecialistOnCall; incident commander can override during a declared incident. | `EscalationDecisionOwner`, v2, approved September 3, 16:00 | Internal; supports roles but not service performance |
| E04 | Three invented routing tests under v2: ordinary after-hours request reached ServiceDesk (`PASS`); priority request with on-call marker reached SpecialistOnCall (`PASS`); missing on-call roster produced no named fallback (`FAIL`). No customer traffic or response-time test occurred. | `SupportEvidenceOwner`, run RT-07, September 4, 11:00 | Internal; A02 must address the failed fallback and must not claim the route is production-ready |
| E05 | Supplier offers a configuration package for USD 4,800, valid through September 10. Scope excludes internal security review, tax and deployment approval. Finance classification and budget owner confirmation are absent. | `SupplierCoordinator`, quote Q-18, September 2, 09:00 | Restricted; cannot support spend approval at AGM080 |
| E06 | Fictional weekly pilot volume: 42 items; 25 ordinary, 11 specialist-review candidates and 6 missing-label exceptions. It contains no trend comparison and no customer outcome. | `SupportEvidenceOwner`, snapshot W36, September 4, 11:20 | Internal one-page asynchronous update for A04 |
| E07 | Draft operator FAQ contains seven questions about labels, fallback, escalation and exception recording. It is marked DRAFT and has no approved customer language. | `MeetingOwner`, v0.4, September 4, 11:30 | Internal comments for A05; not an approved policy |

E02's `5/6 = 83.3%` and `3/6 = 50%` are arithmetic summaries of a tiny fictional record. They do not establish statistically reliable comprehension or predict adoption. E04 has `2/3 = 66.7%` checks passing, but three designed checks are not a success-rate benchmark. The failed scenario is more important to A02 than the percentage.

## S05 — access check and recovery branch

The team plans to use its authorized internal meeting page. At `2026-09-04T13:20:00Z`, `MeetingOwner` checks each required attendee using the same identity they will use for the meeting. E01 opens for all four attendees. E02 returns `ACCESS_DENIED` for `EscalationDecisionOwner`, who does not need it for A02 but is an invited reader. E03 and E04 open for all four. E05 remains restricted and is not linked. E06 and E07 are sent separately for asynchronous use.

At 13:30, `UXEvidenceOwner` produces authorized extract E02a containing exactly the counts and concerns above, with no hidden reviewer comments. At 13:40, `ProductDecisionOwner` verifies E02a against E02. At 13:50, `EscalationDecisionOwner` and `MeetingOwner` successfully open E02a. Agenda v1.0 links E02a, not E02. This recovery demonstrates the planned access check, not a universal workaround. If an authorized extract could not be supplied, A01 would be held or narrowed to identify the missing evidence; the workflow must not tell participants to bypass access controls.

Microsoft currently documents that external attendees cannot access or edit its Teams meeting notes. AGM080's live items use four internal attendees, but this case does not infer that every internal identity or every meeting system has access. A real organizer must test the actual tool, account and document permissions.

## S06 — availability, preparation and change states

All four required attendees accept 14:00–14:35 UTC. `ProductDecisionOwner` and `EscalationDecisionOwner` confirm that their decision authority applies to the internal pilot only. `SupportEvidenceOwner` agrees to answer E03/E04 questions and not introduce customer incidents. The meeting has captions enabled under the team's normal tool configuration; no recording is planned. The case does not test accessibility quality, participant comfort or platform performance.

Pre-work due September 8 at 12:00: all four open agenda v1.0 and E02a; `ProductDecisionOwner` records a preliminary A01 preference with conditions; `EscalationDecisionOwner` checks the fallback boundary; `SupportEvidenceOwner` confirms whether E04 changed. Completion means the named artifact was checked, not that the reader agrees or exerted sufficient effort.

Late-request test LR01 asks what should happen if a ten-minute staffing discussion arrives on September 8 at 13:10 without evidence or a decision owner. Under AR1, `MeetingOwner` would record it for triage after AGM080 and would not alter v1.0. This is a prospective branch, not a received event. If an urgent safety issue were raised, the normal agenda rules would not override the organization's escalation procedure; this fictional packet supplies no such issue.

## S07 — final agenda v1.0

The planned segments total exactly 35 minutes. Decision segments total 22 minutes, or `22/35 = 62.9%` of scheduled time. That is an allocation ratio, not decision quality, productivity or a target for other meetings.

| UTC | Minutes | Agenda ID and type | Bounded question or activity | Owner and required output | Evidence and stop/fallback |
| --- | ---: | --- | --- | --- | --- |
| 14:00 | 5 | P00 · preparation check | Confirm purpose, authority, E02a access and unchanged E04; silently reread the two decision cards | `MeetingOwner`; readiness exceptions recorded | S01, E02a, E03, E04; if a decision owner or required evidence is missing, hold that item |
| 14:05 | 12 | A01+A06 · `LIVE_DECISION` | For the internal pilot queue only, choose “Specialist review” or “Manual review.” Customer wording and workflow redesign are out of scope. | `ProductDecisionOwner`; one choice, conditions, or explicit no-decision reason | E01/E02a; at 14:17 stop. If conditions cannot be resolved, record owner and next evidence instead of forcing a choice |
| 14:17 | 10 | A02 · `LIVE_DECISION` | Choose the after-hours receiver and a named fallback for the missing-roster scenario. Root-cause redesign is out of scope. | `EscalationDecisionOwner`; route, fallback, applicability and verification action—or no decision | E03/E04; at 14:27 stop. Do not call the route production-ready without a later passed check |
| 14:27 | 3 | X00 · exception review | Read back A03 deferred, A04/A05 asynchronous and A06 merged; check no submitted item disappeared | `MeetingOwner`; disposition register confirmed or corrected | S02/S06; this does not reopen deferred subjects |
| 14:30 | 5 | C00 · decision/action readback | Read exact provisional decisions, conditions, dissent, actions, owners, due dates and next verification | Each decision owner confirms only their record; `MeetingOwner` records unresolved points | If confirmation is absent, label the record provisional and route it; do not infer approval from silence |

## S08 — release checklist and empty outcome record

At `2026-09-04T15:00:00Z`, each decision owner confirms their question and boundary, not an answer. `MeetingOwner` releases v1.0 at 15:20 after checking total minutes, four acceptances, working links, asynchronous destinations and dispositions for all six submissions. The release precedes the 16:00 deadline. This is a completed agenda-preparation example; the planned meeting has not occurred in the packet.

The outcome record is deliberately empty until the meeting: A01 decision = `NOT_HELD`; A02 decision = `NOT_HELD`; dissent = `NOT_CAPTURED`; actions = `NOT_CREATED`; attendance = `NOT_OBSERVED`; actual segment durations = `NOT_OBSERVED`. A polished agenda cannot fill these fields prospectively.

## Independent reviewer checks

- Submissions: 6. Distinct topics after A06 merges into A01: 5. Dispositions by submission: two live (A01, A02), two asynchronous (A04, A05), one deferred (A03), one merged (A06). Preserve all six IDs.
- Submitted time: `18 + 15 + 12 + 10 + 8 + 7 = 70` minutes. Remove the duplicate request's 7 minutes to describe 63 minutes of distinct requested demand. Do not call either figure meeting waste.
- Planned agenda: `5 + 12 + 10 + 3 + 5 = 35` minutes. Live decision allocation: `12 + 10 = 22`; `22/35 = 62.9%`. This is not a meeting outcome.
- E02: five of six intended selections for one phrase, three of six for the other. Small invented review record, no claim of significance. E04: two PASS, one FAIL; the failed fallback remains unresolved.
- Attendance: four required internal attendees. Three other roles are not attending for documented reasons. Invited count is not a participation or representation quality score.
- Access: one denial observed in the fictional check; one authorized extract produced and opened by the affected attendee. E05 remains restricted and excluded. Do not claim access checks succeeded for every platform.
- Release: draft 13:00, exception 13:20, extract 13:30, verification 13:40, access retest 13:50, approvals 15:00, release 15:20 against a 16:00 deadline. These are fictional process timestamps, not speed evidence.
- Outcomes remain unobserved. Any completed decision, action, meeting-duration reduction, participant sentiment or OpenMax benefit inserted later would contradict this frozen packet unless a new, explicitly labeled fictional post-meeting edition is authored.

This complete packet is sufficient to reproduce the agenda admission, disposition, access and time-allocation reasoning. It does not establish product accuracy, real integration behavior, legal compliance, meeting effectiveness or customer value.