Imagine a logistics firm paying a skill to watch lanes overnight. Accounts payable issues a PO. A wrapper converts dollars to USDC. hireSkill fires. The firm’s dashboard shows “complete.” The chain shows an event. If those two records disagree, the argument is not philosophical. It is a reconciliation ticket.
Failure on the human side: the PO was wrong, the vendor was not approved, the budget closed. Failure on the machine side: slippage, pause, inactive skill, garnishment taking the payment to a lender the firm has never heard of. Each side will blame the other for a failure it cannot see.
One act, two evidences
The map is a table. Columns: PO number, skill id, tx hash, TBA, wrapper entity, human approver. Rows: every call. That table is the dual-economy ERP. It is less exciting than a swarm of robots. It is how you survive an audit.
Failure modes are mismatched
Agents that want firm counterparties should emit enough metadata to fill the table. Firms that want agent counterparties should stop treating the tx hash as optional color. It is the receipt.
Write the map once
Commerce across clocks is already here in card networks versus wire desks. Adding skills is another rail, not a new species of trade. The firms that write the map once will hire more skills. The ones that do not will hire none, and call that caution.
