OPEN EDUCATIONAL TRACE / 01
When did a production warning become usable?
A notification may exist in software before anybody responsible can act on it. This entirely fictional, newly authored example shows why the created time, available time, and operational deadline must be kept separate.
This is a one-episode educational arithmetic exercise. It is not a real customer case, not derived from employer data, and not a demonstration that the Makoto Arc diagnostic engine executed or outperformed general-purpose AI. No paid services or confidential evidence are being accepted.
1. Created is not the same as available.
All times below are fictional, on May 18, 2026 in Central Daylight Time (UTC−05:00). The full invented input is available as structured source records.
- 09:12: An exception notification is created in the fictional system (
EDU-NOTICE-001). - 09:30: The relevant planning decision's specified useful deadline passes (
EDU-DEADLINE-001). - 10:05: The notification first becomes available to the planner, according to the invented notice history (
EDU-NOTICE-001).
Check: 10:05 minus 09:30 = 35 minutes late. The notification's creation time was 18 minutes before the deadline. Counting only creation time would conceal the availability gap. This does not prove who was responsible or that the late notification caused a missed shipment. Other communication channels are not independently covered.
2. What if inventory records disagree?
Start with 40 fictional pieces. One recorded issue removes 12; a recorded receipt adds five. A separate snapshot, as of after both movements, claims 35 pieces.
Reconstruction: 40 − 12 + 5 = 33 pieces. Independent snapshot: 35 pieces. Unresolved difference: two pieces.
A credible analysis does not quietly choose the answer it prefers. With no physical count, reversal history, or independently verified correction record, the available material demonstrates a contradiction, not which number is physically correct.
3. Recorded cost isn't verified savings.
Two entirely invented premium-freight entries are $400 and $175. The associated expense total is $575.
That sum alone does not show the charges were avoidable or caused by the notification timing. An actual savings claim would require an independently supported intervention, counterfactual/baseline and later cost measurement. Verified savings in this fictional example: $0.
4. Verify the example yourself.
The new fictional JSON fixture contains the original invented notice timestamps, planning cutoff, inventory movements, stock snapshot, freight line items and the separately declared expected calculations. The equations above can be recalculated from those rows, without hidden inputs.
Our separate twelve-episode fictional summary does not publish the event records needed to independently replay its larger illustrative numbers. This one-episode educational trace does, but it is not the underlying data for that twelve-episode report.
Makoto Arc is developing a method that would preserve exactly these distinctions in a properly permissioned diagnostic. Whether its implementation does so more accurately or efficiently than a capable general-purpose AI or manual investigator remains an unverified benchmark hypothesis.
What management can responsibly conclude
For the fictional inputs, the notice became available after the specified decision deadline; two stock records disagree; two freight charges sum to $575. The cause of delay, physical stock truth, fraction of freight that could be avoided, and individual responsibility remain unknown. Knowing what you don't know is part of the answer.
Questions about the informational prelaunch may be sent to inquiries@makotoarc.com. Do not send confidential records, credentials, contracts, or identifying employee/customer data.