Inspect event quality, retain uncertainty and prepare a disciplined human review before considering AI or automation.
Separate fictional message-service experiment. These six authored cases are not MC², the FedCiv case or client telemetry. This is a data-inspection rehearsal, not a readiness score or permission to test.
Test the evidence before asking more of it.
Synthetic sample
Retain every record
Inspect gaps
Identity · time · service
Apply a rule
Transparent associations
Human review
Questions remain open
No model, live telemetry or response action.
Showing case 1 of 6. Selection stays in this tab only.
Recent change and service degradation
Teaching setup. Authored message-service teaching case; same-service proximity offers questions, never cause or authority.
0Withheld from association
1Preserved repeat copy
1Change context
3Signal context
0Recovery signal
5 supplied records. These five roles partition the sample. Observed service identifiers describe this supplied sample only. Missing producers, events or services cannot be detected without an independent inventory and expected delivery evidence.
What the records support
2 investigation candidates from the illustrative 30-minute rule. Candidates are not incidents, causes or proposed responses.
release-1 → memory-1 · 10 minutes · Investigation candidate only. Timing does not establish cause, culpability or a rollback instruction.
release-1 → mission-1 · 12 minutes · Investigation candidate only. Timing does not establish cause, culpability or a rollback instruction.
Root cause: undetermined Restoration: not established Execution: disabled
Which producers, services and periods are absent from this sample?
What independent evidence supports the declared clocks and service mapping?
What still needs agreement
Declared means a fictional planning note is recorded. It is not verified data handling, clock alignment, accepted ownership, permission to test or operational authority.
Handling and retention · Not recorded
What information may be used, where may it remain and who confirms retention?
No declaration supplied. Do not infer agreement from an event count.
Service mapping · Not recorded
Who verifies that source identifiers describe the same service and dependency?
No declaration supplied. Do not infer agreement from an event count.
Clock evidence · Not recorded
What demonstrates occurrence times, clock alignment and any uncertainty?
No declaration supplied. Do not infer agreement from an event count.
Service verification · Not recorded
Which user-visible result and retained dependencies would establish recovery?
No declaration supplied. Do not infer agreement from an event count.
Human review · Not recorded
Who reviews associations, records competing explanations and accepts follow-up?
No declaration supplied. Do not infer agreement from an event count.
Permission to test, accepted owner and agreed date: not established.
Inspect the retained records
Clocks marked “verified” are input declarations, not clock measurements made by this tool. Withheld records and repeated deliveries remain inspectable.
release-1 · Change context
Recorded statement
Worker configuration release recorded. Its relationship to degradation is unknown.
synthetic://incident-rehearsal/memory-1 · Authored teaching event; no live system or individual is represented.
Copy retained; does not multiply investigation candidates.
Evaluate the assistance, not the appearance of certainty
Human review time and dispositions are not measured. Candidate counts cannot prove time saved, accuracy, noise reduction or reduced review effort.
For a later bounded evaluation, record whether a candidate was useful, unsupported or required more context; retain competing explanations and measure reviewer effort against the same rules baseline. New held-out cases and a client-approved testing boundary remain future work.
Teaching setup. Authored message-service teaching case; same-service proximity offers questions, never cause or authority.
3Withheld from association
0Preserved repeat copy
1Change context
1Signal context
0Recovery signal
5 supplied records. These five roles partition the sample. Observed service identifiers describe this supplied sample only. Missing producers, events or services cannot be detected without an independent inventory and expected delivery evidence.
What the records support
0 investigation candidates from the illustrative 30-minute rule. Candidates are not incidents, causes or proposed responses.
No association offered. This does not rule out a relationship.
Root cause: undetermined Restoration: not established Execution: disabled
Reconcile withheld records before relying on the time-association filter.
Which producers, services and periods are absent from this sample?
What independent evidence supports the declared clocks and service mapping?
What still needs agreement
Declared means a fictional planning note is recorded. It is not verified data handling, clock alignment, accepted ownership, permission to test or operational authority.
Handling and retention · Not recorded
What information may be used, where may it remain and who confirms retention?
No declaration supplied. Do not infer agreement from an event count.
Service mapping · Not recorded
Who verifies that source identifiers describe the same service and dependency?
No declaration supplied. Do not infer agreement from an event count.
Clock evidence · Not recorded
What demonstrates occurrence times, clock alignment and any uncertainty?
No declaration supplied. Do not infer agreement from an event count.
Service verification · Not recorded
Which user-visible result and retained dependencies would establish recovery?
No declaration supplied. Do not infer agreement from an event count.
Human review · Not recorded
Who reviews associations, records competing explanations and accepts follow-up?
No declaration supplied. Do not infer agreement from an event count.
Permission to test, accepted owner and agreed date: not established.
Inspect the retained records
Clocks marked “verified” are input declarations, not clock measurements made by this tool. Withheld records and repeated deliveries remain inspectable.
release-1 · Change context
Recorded statement
Worker configuration release recorded. Its relationship to degradation is unknown.
synthetic://incident-rehearsal/memory-1 · Authored teaching event; no live system or individual is represented.
Retained; not used for time association.
Evaluate the assistance, not the appearance of certainty
Human review time and dispositions are not measured. Candidate counts cannot prove time saved, accuracy, noise reduction or reduced review effort.
For a later bounded evaluation, record whether a candidate was useful, unsupported or required more context; retain competing explanations and measure reviewer effort against the same rules baseline. New held-out cases and a client-approved testing boundary remain future work.
Teaching setup. Authored message-service teaching case; same-service proximity offers questions, never cause or authority.
2Withheld from association
0Preserved repeat copy
1Change context
2Signal context
0Recovery signal
5 supplied records. These five roles partition the sample. Observed service identifiers describe this supplied sample only. Missing producers, events or services cannot be detected without an independent inventory and expected delivery evidence.
What the records support
1 investigation candidates from the illustrative 30-minute rule. Candidates are not incidents, causes or proposed responses.
release-1 → security-1 · 13 minutes · Investigation candidate only. Timing does not establish cause, culpability or a rollback instruction.
Root cause: undetermined Restoration: not established Execution: disabled
Reconcile withheld records before relying on the time-association filter.
Which producers, services and periods are absent from this sample?
What independent evidence supports the declared clocks and service mapping?
What still needs agreement
Declared means a fictional planning note is recorded. It is not verified data handling, clock alignment, accepted ownership, permission to test or operational authority.
Handling and retention · Not recorded
What information may be used, where may it remain and who confirms retention?
No declaration supplied. Do not infer agreement from an event count.
Service mapping · Not recorded
Who verifies that source identifiers describe the same service and dependency?
No declaration supplied. Do not infer agreement from an event count.
Clock evidence · Not recorded
What demonstrates occurrence times, clock alignment and any uncertainty?
No declaration supplied. Do not infer agreement from an event count.
Service verification · Not recorded
Which user-visible result and retained dependencies would establish recovery?
No declaration supplied. Do not infer agreement from an event count.
Human review · Not recorded
Who reviews associations, records competing explanations and accepts follow-up?
No declaration supplied. Do not infer agreement from an event count.
Permission to test, accepted owner and agreed date: not established.
Inspect the retained records
Clocks marked “verified” are input declarations, not clock measurements made by this tool. Withheld records and repeated deliveries remain inspectable.
release-1 · Change context
Recorded statement
Worker configuration release recorded. Its relationship to degradation is unknown.
synthetic://incident-rehearsal/memory-1 · Authored teaching event; no live system or individual is represented.
Retained; not used for time association.
Evaluate the assistance, not the appearance of certainty
Human review time and dispositions are not measured. Candidate counts cannot prove time saved, accuracy, noise reduction or reduced review effort.
For a later bounded evaluation, record whether a candidate was useful, unsupported or required more context; retain competing explanations and measure reviewer effort against the same rules baseline. New held-out cases and a client-approved testing boundary remain future work.
Teaching setup. Authored message-service teaching case; same-service proximity offers questions, never cause or authority.
0Withheld from association
1Preserved repeat copy
1Change context
3Signal context
1Recovery signal
6 supplied records. These five roles partition the sample. Observed service identifiers describe this supplied sample only. Missing producers, events or services cannot be detected without an independent inventory and expected delivery evidence.
What the records support
2 investigation candidates from the illustrative 30-minute rule. Candidates are not incidents, causes or proposed responses.
release-1 → memory-1 · 10 minutes · Investigation candidate only. Timing does not establish cause, culpability or a rollback instruction.
release-1 → mission-1 · 12 minutes · Investigation candidate only. Timing does not establish cause, culpability or a rollback instruction.
Root cause: undetermined Restoration: not established Execution: disabled
Which producers, services and periods are absent from this sample?
What independent evidence supports the declared clocks and service mapping?
What still needs agreement
Declared means a fictional planning note is recorded. It is not verified data handling, clock alignment, accepted ownership, permission to test or operational authority.
Handling and retention · Not recorded
What information may be used, where may it remain and who confirms retention?
No declaration supplied. Do not infer agreement from an event count.
Service mapping · Not recorded
Who verifies that source identifiers describe the same service and dependency?
No declaration supplied. Do not infer agreement from an event count.
Clock evidence · Not recorded
What demonstrates occurrence times, clock alignment and any uncertainty?
No declaration supplied. Do not infer agreement from an event count.
Service verification · Not recorded
Which user-visible result and retained dependencies would establish recovery?
No declaration supplied. Do not infer agreement from an event count.
Human review · Not recorded
Who reviews associations, records competing explanations and accepts follow-up?
No declaration supplied. Do not infer agreement from an event count.
Permission to test, accepted owner and agreed date: not established.
Inspect the retained records
Clocks marked “verified” are input declarations, not clock measurements made by this tool. Withheld records and repeated deliveries remain inspectable.
release-1 · Change context
Recorded statement
Worker configuration release recorded. Its relationship to degradation is unknown.
synthetic://incident-rehearsal/recovery-1 · Authored teaching event; no live system or individual is represented.
Health signal retained; not service-restoration proof.
Evaluate the assistance, not the appearance of certainty
Human review time and dispositions are not measured. Candidate counts cannot prove time saved, accuracy, noise reduction or reduced review effort.
For a later bounded evaluation, record whether a candidate was useful, unsupported or required more context; retain competing explanations and measure reviewer effort against the same rules baseline. New held-out cases and a client-approved testing boundary remain future work.
Teaching setup. Author-controlled omission: the security-alert source was removed. The inspector sees no structural error in the remaining records. It cannot discover a silent source without an independently confirmed expected inventory.
0Withheld from association
1Preserved repeat copy
1Change context
2Signal context
0Recovery signal
4 supplied records. These five roles partition the sample. Observed service identifiers describe this supplied sample only. Missing producers, events or services cannot be detected without an independent inventory and expected delivery evidence.
What the records support
2 investigation candidates from the illustrative 30-minute rule. Candidates are not incidents, causes or proposed responses.
release-1 → memory-1 · 10 minutes · Investigation candidate only. Timing does not establish cause, culpability or a rollback instruction.
release-1 → mission-1 · 12 minutes · Investigation candidate only. Timing does not establish cause, culpability or a rollback instruction.
Root cause: undetermined Restoration: not established Execution: disabled
Which producers, services and periods are absent from this sample?
What independent evidence supports the declared clocks and service mapping?
What still needs agreement
Declared means a fictional planning note is recorded. It is not verified data handling, clock alignment, accepted ownership, permission to test or operational authority.
Handling and retention · Not recorded
What information may be used, where may it remain and who confirms retention?
No declaration supplied. Do not infer agreement from an event count.
Service mapping · Not recorded
Who verifies that source identifiers describe the same service and dependency?
No declaration supplied. Do not infer agreement from an event count.
Clock evidence · Not recorded
What demonstrates occurrence times, clock alignment and any uncertainty?
No declaration supplied. Do not infer agreement from an event count.
Service verification · Not recorded
Which user-visible result and retained dependencies would establish recovery?
No declaration supplied. Do not infer agreement from an event count.
Human review · Not recorded
Who reviews associations, records competing explanations and accepts follow-up?
No declaration supplied. Do not infer agreement from an event count.
Permission to test, accepted owner and agreed date: not established.
Inspect the retained records
Clocks marked “verified” are input declarations, not clock measurements made by this tool. Withheld records and repeated deliveries remain inspectable.
release-1 · Change context
Recorded statement
Worker configuration release recorded. Its relationship to degradation is unknown.
synthetic://incident-rehearsal/memory-1 · Authored teaching event; no live system or individual is represented.
Copy retained; does not multiply investigation candidates.
Evaluate the assistance, not the appearance of certainty
Human review time and dispositions are not measured. Candidate counts cannot prove time saved, accuracy, noise reduction or reduced review effort.
For a later bounded evaluation, record whether a candidate was useful, unsupported or required more context; retain competing explanations and measure reviewer effort against the same rules baseline. New held-out cases and a client-approved testing boundary remain future work.
Teaching setup. Three planning notes are present, but the same clock and service gaps remain. Documentation quantity cannot repair the underlying event evidence.
3Withheld from association
0Preserved repeat copy
1Change context
1Signal context
0Recovery signal
5 supplied records. These five roles partition the sample. Observed service identifiers describe this supplied sample only. Missing producers, events or services cannot be detected without an independent inventory and expected delivery evidence.
What the records support
0 investigation candidates from the illustrative 30-minute rule. Candidates are not incidents, causes or proposed responses.
No association offered. This does not rule out a relationship.
Root cause: undetermined Restoration: not established Execution: disabled
Reconcile withheld records before relying on the time-association filter.
Which producers, services and periods are absent from this sample?
What independent evidence supports the declared clocks and service mapping?
What still needs agreement
Declared means a fictional planning note is recorded. It is not verified data handling, clock alignment, accepted ownership, permission to test or operational authority.
Handling and retention · Planning note recorded
What information may be used, where may it remain and who confirms retention?
Fictional declaration: Fictional discussion proposes a local-only synthetic dataset. No approval or real-data boundary is established.
Reference: synthetic://planning/handling-draft
Service mapping · Not recorded
Who verifies that source identifiers describe the same service and dependency?
No declaration supplied. Do not infer agreement from an event count.
Clock evidence · Planning note recorded
What demonstrates occurrence times, clock alignment and any uncertainty?
Fictional declaration: Fictional team says clocks should be aligned; alignment evidence is still needed.
Reference: synthetic://planning/clock-question
Service verification · Not recorded
Which user-visible result and retained dependencies would establish recovery?
No declaration supplied. Do not infer agreement from an event count.
Human review · Planning note recorded
Who reviews associations, records competing explanations and accepts follow-up?
Fictional declaration: An operations reviewer is proposed; nobody has accepted and no review time has been measured.
Reference: synthetic://planning/reviewer-role
Permission to test, accepted owner and agreed date: not established.
Inspect the retained records
Clocks marked “verified” are input declarations, not clock measurements made by this tool. Withheld records and repeated deliveries remain inspectable.
release-1 · Change context
Recorded statement
Worker configuration release recorded. Its relationship to degradation is unknown.
synthetic://incident-rehearsal/memory-1 · Authored teaching event; no live system or individual is represented.
Retained; not used for time association.
Evaluate the assistance, not the appearance of certainty
Human review time and dispositions are not measured. Candidate counts cannot prove time saved, accuracy, noise reduction or reduced review effort.
For a later bounded evaluation, record whether a candidate was useful, unsupported or required more context; retain competing explanations and measure reviewer effort against the same rules baseline. New held-out cases and a client-approved testing boundary remain future work.
Existing 12 frozen incident-rule regression cases. Does not test the new planning contract or demonstrate AI performance.
Originally authored separately before rule-body inspection. Now a known regression set, not a fresh held-out evaluation. Passing the coincidental-change case demonstrates a limitation, not causal accuracy.
Actual runner output · 2026-11-02T09:00:35.550Z
PASS eval-01: Interior window positive control
PASS eval-02: Inclusive 30-minute and zero boundaries; millisecond outside and future excluded
PASS eval-03: Unverified change clock cannot associate despite plausible timestamps
PASS eval-04: Received time cannot supply missing signal occurrence
PASS eval-05: Unknown change or signal service abstains
PASS eval-06: Cross-service proximity does not become dependency association
PASS eval-07: Conflicting change identity excludes every conflicting copy
PASS eval-08: Conflicting signal identity excludes every conflicting copy
PASS eval-09: Repeated deliveries remain visible without multiplying pairs
PASS eval-10: Equal record IDs from unique producers remain distinct
PASS eval-11: Recovery signal is retained but does not prove restoration
PASS eval-12: Coincidental unrelated same-service change passes proximity filter
12/12 cases pass; 0 retained failures.