Demo · The Safety-Verified Craft Packet (Kiewit Concept, Independent)

Concept mock. Act 1 paraphrases the real outcome of an agent reading Kiewit's live llms.txt (a content index; no agent card, no verification). All names, tasks, and receipts in Act 2 are fabricated demonstrations running EcoWealth's packet format. Not affiliated with or endorsed by Kiewit.

Owner's AI: "Kiewit publishes an llms.txt, good. It says '140 years of self-perform expertise' and lists the Salton Sea habitat project. For the erosion-control lift completed there last week, was it done safely, by whom, and can I verify it?"

Reading kiewit.com/llms.txt (today)I can point you to the project page and the safety philosophy ("Nobody Gets Hurt"). For the specific task, there's nothing here to act on: no agent card, no tools, no verifiable receipt. The door is open; the room is a brochure.source: /llms.txt (content index) · agent-card.json 404

"So you can read about Kiewit, but not verify Kiewit."

Owner's AIExactly. Kiewit is ahead, the front door exists. It just doesn't lead anywhere an agent can transact or verify yet.

Door's open. The room, that's Act 2. →

⚙

1 · Authoring hits the hazard gate first

A Kiewit engineer (or their agent, via x402 (a web-native way for AI agents to pay per use), $0.10) drafts the packet: erosion-control & native revegetation lift, Salton Sea habitat cell 4. The machine gate validates hazard class, required controls, and framing before the packet can exist. A version that skips the required controls is rejected automatically, same gate that runs on our live library in CI.

$ work:validate packet-draft.json ✗ REJECTED: hazard_class: heavy_equipment_near_water requires spotter + spill_kit in controls[] $ work:validate packet-draft-v2.json ✓ PASS: hazards[2] mapped, controls[4] complete → packet EWP-K-SS4 posted

⇄

2 · A self-perform craft crew claims it

The packet routes to Kiewit's own craft crew, claim is signed by the crew's wallet (browser wallet or passkey; no new accounts, no app to install). Because the workforce is self-perform and employee-owned, the crew that owns the work also owns the receipt. Pay follows the proof.

✓

3 · Proof of safe completion, checked deterministically

The crew closes with photos of the controls + spotter/spill-kit evidence + GPS + timestamp + signature. A deterministic proof-checker (agent-payable, $0.01) returns the verdict: no proof, no settlement.

$ x402 POST /work-proof-check ($0.01) verdict: PASS · photos: 4/4 geotagged on-site · spotter present · signer matches claim

⛓

4 · Settlement writes the receipt that compounds

Approval settles on Base, a public, permanent receipt: this craft task, this crew, these controls, verified this morning. It's an internal quality record and, for this Restore-ladder habitat work, carries the tCO2e/habitat outcome into a machine-verifiable ESG line.

SettlementRecorded → base mainnet · EWP 0x76c17C…A14B receipt: verified-safe work · verified done · verified paid · owned by the crew (pattern proven live: workId 14, first settled packet, 2026-07-07)

This is not vaporware, walk the real path today. The packet engine, hazard gate, proof-checker, and on-chain settlement all run now on EcoWealth's own work board: live walkthrough at vealth.net/receipts/building-agent-demo/ · contract 0x76c17C…A14B on BaseScan · live board counters at vealth.net/labor/stats (with stream_bioassessment and watershed_outfall_screen lanes that mirror Kiewit's own Salton Sea / Cleaning-the-Creek work) · agent pricing at vealth.net/.well-known/x402.

← Hub · Capability brief · Agent Kit →

EcoWealth Corporation · [email protected] · Independent concept, unlisted, noindex. Fabricated demo data; no Kiewit systems touched; no affiliation or endorsement implied.

Act 1: the agent reads your open door. Act 2: it verifies your work.

1 · Authoring hits the hazard gate first

2 · A self-perform craft crew claims it

3 · Proof of safe completion, checked deterministically

4 · Settlement writes the receipt that compounds