Turner already leads the industry's safety culture: Building L.I.F.E.®, ISO 45001, and now SafeT Coach, an AI safety consultant shared free with the whole industry. This concept adds the missing layer under it: machine-verified proof that work was done safely, built from hazard-gated authoring, proof-of-safe-completion, and a settlement receipt on a public chain. Verified-safe work, verified done, verified paid.
We found that Turner shipped a real AI safety advisor, but it can only give advice, not prove a task was actually done safely. We drafted the missing proof layer, free: a demo showing a safety-gated work packet that can't even be created without passing a hazard check, then settles to a permanent receipt. The one ask: fifteen minutes, only if this reaches the right person through a conversation they started.
llms.txt (the file AI assistants read first) is a true 404.Baseline credited first (it's strong). Then four evidenced findings: the advice/verification gap, the self-attested prequal file, the machine-illegible commitments, and one small hygiene note, each with the exact URL, HTTP status, and re-check command.
Read the briefTwo acts in Turner's own palette: Act 1, a worker asks an AI coach and gets advice (today, real). Act 2, the same task becomes a work packet that cannot be authored without passing a machine hazard gate, is completed with photo+GPS+signature proof, and settles to an on-chain receipt the sub's safety file can cite forever.
Run the demoConcept files: an llms.txt that makes SafeT Coach and the prequal door discoverable, an agent card, MCP tool schemas (the standard AI apps call for live actions) for verified safety history, and a concierge persona. Drafts, ready to hand to Turner's own team.
construction_site_safety_walk and civic_hazard_survey lanes; proof-checked packets (photo+GPS+signature); on-chain settlement on Base: EWP contract 0x76c17C…A14B, first settled packet workId 14; agent-payable tools over x402 (work-packet $0.10 · work-proof-check $0.01); and a live end-to-end agent walkthrough: the building-agent golden path.
No account, no API key, no sales call: the work-packet endpoint is live, and an agent can complete the loop in an afternoon.
Give any AI agent, Claude, GPT-class, Llama, or your own, a Base wallet holding a few cents of USDC. That's the entire setup.
The work-packet program answers HTTP 402 with a standard x402 payment schema; the agent signs a USDC authorization and pays $0.10. A runnable client with a dry-run default is at vealth.net/recipes.html.
Back comes a bounded, proof-verified work packet, and every step the agent took (payment, settlement) is an on-chain receipt anyone can verify, forever.
work-packet call and settle a single safety-verified packet: the same rail in the proof stack above, no Turner systems access.