# Decision log: complete fictional case packet This is original OpenMax editorial teaching material, not customer data, an actual pilot, product execution, a security incident report or professional advice. All people are fictional assigned roles. All timestamps are UTC in 2026. Snapshot: 2026-08-31T12:00:00Z. The eight short documents below are the complete invented source texts for the decision exercise; no longer hidden originals are implied. The action ledger is a separate complete fictional follow-up record. Do not use these dates as article publication dates. ## Original source documents S01–S08 ### S01 — authority memo, 2026-08-24T09:00Z The operations lead may authorize or pause an internal drafting pilot for OPS-A and OPS-B using approved written meeting notes. This remit excludes customer meetings, audio/video recordings and personnel or HR records. Expansion to those categories requires a separately established authority and specialist review; this memo grants none. The project coordinator maintains the register. A source-access problem must reach the operations lead for review within 24 hours. Reporting a problem alone does not automatically reverse a decision. Each decision states its effective time and any prerequisites. ### S02 — options memo, 2026-08-25T08:00Z We can continue manual notes or trial drafting assistance for authorized internal written notes with human review before internal distribution. Manual notes remain workable. The trial could inform whether drafting is useful, but effort savings and quality are unmeasured. Compare permitted inputs, review workload, reversibility and ability to verify sources. Customer-meeting expansion is outside S01 authority and is not a feasible launch option for today's decision. No tool implementation or successful trial is evidenced by this memo. ### S03 — D078-01 decision statement, 2026-08-25T10:00Z As operations lead under S01, I accept a limited internal drafting pilot for OPS-A and OPS-B. It takes effect 2026-08-26T09:00Z, covers only authorized supplied written notes and requires human review before internal distribution. Customer meetings, recordings and HR records are excluded. Review is scheduled for 2026-08-31T09:00Z. The initial end is 2026-09-09T09:00Z unless a replacement applies earlier. We choose the reversible pilot over continuing entirely manual notes to learn whether the drafting method is useful; we accept added review work and do not claim savings. Source-access problems trigger owner review within 24 hours, not automatic cancellation. The coordinator will communicate limits and schedule a September 1 pilot check. Manual notes remain the fallback. ### S04 — record confirmation, 2026-08-25T11:30Z The operations lead confirms that the published D078-01 record accurately captures S03. The decision was made at 10:00Z; this is record confirmation at 11:30Z, not a second decision or a changed effective time. ### S05 — D078-02 proposal, 2026-08-28T10:00Z The project coordinator proposes exploring extension to customer meetings. No authorized decider for that extension has been established in this packet. Approval, handling conditions and effective time are not recorded. Retaining the internal-only scope remains possible. This proposal does not replace D078-01. It does not grant permission to record or process customer conversations. ### S06 — reviewer report, 2026-08-30T12:00Z While reviewing one internal draft, the assigned reviewer cannot open a cited source. The cause is not yet known. This report does not establish a disclosure incident, an error rate or a failure affecting every draft. The reviewer refers the issue to the operations lead under the 24-hour review rule. ### S07 — D078-03 decision statement, 2026-08-30T16:00Z As operations lead under S01, I accept pausing the internal drafting pilot from 2026-08-31T09:00Z and using manual notes. D078-03 supersedes D078-01 from that effective time, not before it. We choose pause over unchanged continuation because S06 leaves the intended source-checking process unresolved and manual notes remain available. This does not approve D078-02. The coordinator must notify both teams by the effective time; the reviewer must reproduce and document the problem by 2026-09-01T12:00Z. Notification is an implementation action, not a stated condition delaying effectiveness. Restart requires a new authorized decision after evidence review; completing an investigation alone does not restart the pilot. Cancel scheduling of the September 1 pilot check. No savings, incident finding or technical root cause is asserted. ### S08 — record confirmation, 2026-08-30T17:00Z The operations lead confirms that the published D078-03 record accurately captures S07. Acceptance was at 16:00Z, recording confirmation is at 17:00Z, and effectiveness remains 2026-08-31T09:00Z. D078-01 points to D078-03 at that boundary. The coordinator marks the scheduling action cancelled. No completed notification or completed investigation is recorded here. ## Filled record D078-01 ### 1. ID, lifecycle and timestamps D078-01, internal written-notes drafting pilot. Decision-body version1; lifecycle view verified at the snapshot. Accepted2026-08-25T10:00Z/S03; record confirmed11:30Z/S04; effective08-26T09:00Z. Review08-31T09:00Z; original end09-09T09:00Z. At snapshot superseded by D078-03 from08-31T09:00Z. No predecessor. Later state link does not rewrite the original rationale. ### 2. Bounded question May OPS-A and OPS-B trial drafting from authorized internal written meeting notes during the stated period? Excludes customer meetings, recordings and HR records. Customer expansion is a separate question. ### 3. Authority and roles Operations lead decides under S01. Coordinator maintains the register and communicates. Assigned reviewer checks drafts and reports source problems. Both pilot teams receive the limits. No customer-processing authority is established. ### 4. Context and constraints The team wants to learn whether draft assistance is useful; no measured savings or quality result exists. Manual notes remain workable. Authorized written inputs and review before distribution constrain the pilot. ### 5. Alternatives Continue manual notes or run a limited internal pilot. Compare input permission, review workload, reversibility and source verification. Customer expansion is excluded for lack of authority, not a ready alternative scored poorly. ### 6. Evidence and assumptions S01 establishes remit; S02 describes options; S03 records the choice; S04 confirms the record. Usefulness and effort savings remain assumptions. The original record cannot cite S06 as evidence known on August25. Sources are fictional role-only teaching material, with no real restricted data. ### 7. Outcome and rationale Accept limited drafting from the effective time, with human review and exclusions. Choose a reversible learning exercise over fully manual continuation; accept extra review burden without claiming savings. ### 8. Dissent, risk and conditions No explicit dissent is recorded; that does not prove unanimous agreement. Usefulness is unknown. Source-access issue requires owner review within24h, not automatic cancellation. Human review before internal distribution remains a working rule. ### 9. Actions and communication A01 confirms/publishes the record, A02 communicates limits, A03 schedules the September1 check. Detailed owners, due times and states are in the complete action ledger. A03 is later cancelled, not completed. ### 10. Review and history S06 triggers early review; S07 accepts the replacement within4h. Link to D078-03 effective08-31T09:00Z, preserving the original reasoning. S08 confirms the history link. No transcription correction or redaction is part of this fictional packet. ## Filled record D078-02 ### 1. ID, lifecycle and timestamps D078-02, customer-meeting expansion proposal, version1. Proposed08-28T10:00Z/S05; no acceptance, record-approval or effective timestamp. Still proposed at the snapshot; no supersession relationship. ### 2. Bounded question Should a future pilot include customer meetings? This is separate from internal written notes and cannot reuse their authorization. ### 3. Authority and roles Coordinator proposes. S01 does not authorize the operations lead to approve this extension. Appropriate decision authority and specialist review are not established in the packet. Do not invent names or approvals. ### 4. Context and constraints An internal pilot exists when the proposal is written. Customer-meeting input and permission requirements have not been resolved. No customer material is supplied; remaining internal-only is viable. ### 5. Alternatives Keep internal scope, or explore a separately authorized extension. These are choices to investigate, not an approved ranking or launch recommendation. Compare the same input, review, reversibility and source-checking criteria after the missing prerequisites are resolved. ### 6. Evidence and assumptions S05 establishes only a proposal. S01 limits the current remit. No approval, customer permission, implementation or benefit evidence is present. ### 7. Outcome and rationale No decision recorded. Do not put the requested expansion in the approved-outcome field. No accepted rationale exists to reconstruct. ### 8. Dissent, risk and conditions Authority and handling questions are unresolved. No recorded dissent or rejection should be invented. Pending does not mean rejected, and it does not mean approved. ### 9. Actions and communication No committed implementation action or deadline is recorded for this proposal. A future owner must establish the review route before work is authorized. Do not manufacture an action as if already assigned. ### 10. Review and history No scheduled review, predecessor or successor is recorded. D078-03 explicitly does not approve this proposal. It remains proposed at the snapshot. ## Filled record D078-03 ### 1. ID, lifecycle and timestamps D078-03, pause the internal drafting pilot, version1. Accepted08-30T16:00Z/S07; record confirmed17:00Z/S08; effective08-31T09:00Z. Current at the snapshot, with implementation gaps still visible. ### 2. Bounded question Should the internal drafting pilot continue while the reported source-access problem remains unresolved? Scope remains OPS-A/OPS-B internal written notes; customer expansion is not authorized. ### 3. Authority and roles Operations lead decides underS01. Coordinator notifies teams. Assigned reviewer investigates. Both teams receive the current instruction; notification completion must be checked independently. ### 4. Context and constraints S06 reports one inaccessible citation, cause unknown. Source review is part of the intended method. Manual notes remain available. Do not infer a real incident or whole-system failure. ### 5. Alternatives Continue unchanged, or pause and use manual notes while investigating. Compare ability to check sources, review burden and reversibility. Expansion is neither authorized nor a solution to this unresolved problem. ### 6. Evidence and assumptions S01 supplies authority, S03 prior limits, S06 the issue, S07 the new choice and S08 record confirmation. Root cause and implementation completion remain unknown. ### 7. Outcome and rationale Pause from08-31T09:00Z. Manual notes support continuity while the intended source-checking method is unresolved. Accept interruption of the learning exercise. A fresh authorized decision is required before restart. ### 8. Dissent, risk and conditions No explicit dissent is recorded. Notification may be incomplete and is checked throughA04. S07 defines notification as an action, not a prerequisite delaying the effective time. Investigating the issue does not itself permit restart. ### 9. Actions and communication A04notify both teams by08-31T09:00Z; A05reproduce/document issue by09-01T12:00Z. A03old scheduling task cancelled. At snapshotA04/A05open; do not report all teams informed. ### 10. Review and history SupersedesD078-01 from08-31T09:00Z; reverse link confirmedS08. Investigation evidence due09-01T12:00Z must be reviewed before any new restart decision. No automatic expiry/restart is stated. D078-02remainsproposed. ## Complete ten-event decision timeline | Event | Timestamp UTC | Source / record | Meaning | | --- | --- | --- | --- | | E01 | 2026-08-24T09:00Z | S01 | Internal decision remit established | | E02 | 2026-08-25T08:00Z | S02 | Options and unmeasured benefits documented | | E03 | 2026-08-25T10:00Z | S03 / D078-01 | Limited pilot accepted | | E04 | 2026-08-25T11:30Z | S04 | Record confirmed | | E05 | 2026-08-26T09:00Z | S03 effective boundary | Pilot instruction effective | | E06 | 2026-08-28T10:00Z | S05 / D078-02 | Customer expansion proposed only | | E07 | 2026-08-30T12:00Z | S06 | Access issue triggers owner review | | E08 | 2026-08-30T16:00Z | S07 / D078-03 | Future pause accepted | | E09 | 2026-08-30T17:00Z | S08 | New record and replacement link confirmed | | E10 | 2026-08-31T09:00Z | S07 effective boundary | Pause replaces limited pilot instruction | ## Complete five-action ledger This fictional ledger supplies all follow-up observations used by the article. DONE entries are invented teaching observations, not execution evidence from a product. State is frozen2026-08-31T12:00Z. | ID | Decision | Owner | Deliverable | Due UTC | State | Completion/cancellation time UTC | Evidence | | --- | --- | --- | --- | --- | --- | --- | --- | | A01 | D078-01 | Recorder | Publish confirmed record | 2026-08-25T12:00Z | DONE | 2026-08-25T11:30Z | S04 confirms published record | | A02 | D078-01 | Coordinator | Communicate pilot limits to both teams | 2026-08-26T09:00Z | DONE | 2026-08-26T08:30Z | Ledger entry: limits distributed to OPS-A and OPS-B | | A03 | D078-01 | Coordinator | Schedule Sept1pilotcheck | 2026-08-31T15:00Z | CANCELLED | 2026-08-30T17:00Z | S07/S08 cancel scheduling | | A04 | D078-03 | Coordinator | Notify both teams of pause | 2026-08-31T09:00Z | OPEN | NONE | No completion evidence recorded | | A05 | D078-03 | Reviewer | Reproduce/document access problem | 2026-09-01T12:00Z | OPEN | NONE | No completion evidence recorded | ## Independent reading and arithmetic checks - At2026-08-30T18:00Z:D078-01current;D078-03acceptedbutnotyet effective;D078-02proposed. - At2026-08-31T10:00Z:D078-03current;D078-01superseded;D078-02proposed. Current instruction is not proof of implementation. - D078-01record latency:11:30−10:00=90minutes. D078-03:17:00−16:00=60minutes. Median(60+90)/2=75minutes. D078-02has no applicable approved-record interval; not zero. - Trigger review:Aug30 16:00−12:00=4hours, within the fictional24hourrule. The new decision becomes effective21hours after the trigger and17hours after acceptance; these are different intervals. - At snapshotA04overdue by3hours;A05notdue. Among2open actions1overdue. CancelledA03notcompleted. - Completed excluding cancellations=2/4=50%; completed across allrows=2/5=40%. Neither measures decision quality, implementation assurance or business value. - Eight decision-source documents, three decision records, ten timeline events and five actions are different units. Do not add them into a count of decisions.