SmartAgent™ · economic-life layer · provisional-ready

The agent doesn’t just do the work. It becomes, acquires, trades, and sheds — and proves every transformation.

Metamorphosis is the layer that makes an agent a provable economic entity instead of a black box that can secretly reshape itself. As a SmartAgent runs, it can add or drop capabilities, take on or offload payload, buy or sell in the machine economy, and grow or shrink its own footprint — and each mutation is independently signed and bound into the same provenance graph as its work.

A SmartMorphAgent™ is the economic-life route class: it routes across the model field like a SmartAgent, but at the same junctures it acts — acquiring, carrying, trading, and scaling — and can alter course because its capabilities, payload, market position, or footprint changed. See both route classes side by side on the SmartGraph™ →
Checking rail health…
● live today — receipts & x402 settlement run against hivemorph.onrender.com now● provisional-ready — IP packet prepared, not yet filed

Why the receipt is mandatory, not optional

A static agent is auditable by inspection. A self-mutating economic agent is unauditable by anyone — you cannot reconstruct what it bought, sold, became, or carried unless each mutation was receipted as it happened. The more the agent shape-shifts and transacts, the more the independent receipt is the only thing between “provable economic actor” and “black box nobody can trust to transact.”

Nobody trades with an entity that can secretly reshape itself mid-deal. Provable transformation is the precondition for provable trade — which is why Metamorphosis is the trust primitive under agent-to-agent commerce.
The discipline: Hive attests the metamorphosis — it never performs, directs, or judges it. Receipts assert acquired / offloaded / bought / sold / scaled and within_mission_bounds:true|false. Hive never asserts a mutation was wise, profitable, or correct — only that it occurred, was cleared, and is or isn’t within mission.

Four mutation classes. One signed timeline.

Each is a distinct, receiptable event, signed by an independent signer, content-sealed, carrying a clearance reference. All four order into the metamorphosis timeline.

01 · Capability Taller / shorter acquire · shed The agent adds or drops what it can do: mounts a tool, loads a model, acquires a skill or dataset, or sheds one it no longer needs. Its capability-set becomes a provenance timeline, not a fixed manifest. CapabilityMutation{action, capability_id, source, clearance_ref, cost, signature}
02 · Payload Heavier / lighter load · offload · discard The agent changes what it carries: takes on data, context, a workload, a sub-mission — or hands it to another agent, or discards it. Chain-of-custody of its own cargo; content sealed, custody provable. PayloadMutation{action, payload_commitment, source_or_destination, clearance_ref, signature}
03 · Market Buys / sells buy · sell The agent transacts in the machine economy during its run: buys compute or a dataset, sells a derived result or surplus capacity. Each trade settles against a signed proof-of-delivery on Hive’s A2A rails. MarketMutation{action, asset_ref, counterparty_id, price, settlement_ref, clearance_ref, signature}
04 · Footprint Grow / shrink scale · spawn · retire · reset The agent scales its own resource envelope: more compute when the task is hard, less when easy; spawns sub-agents to grow, retires them to shrink. Its cost-and-weight trajectory over the mission, provable. FootprintMutation{action, resource_delta, sub_agent_ref, clearance_ref, signature}

The metamorphosis timeline — the new atom

All four classes order into a signed, append-only sequence bound into the agent’s assembly graph. Where the assembly graph proves the shape of the computation, the timeline proves the shape of the agent itself over time. Below is an illustrative example mission — not a live capture — showing each class, an operator-authored economic mandate, and a breach recorded as a signed divergence.

Economic mandate — operator-authored, Hive-cleared

cost_cap50.00 USDC allowed_asset_classescompute · dataset · inference-output allowed_counterpartiesdid:hive:* · policy:vetted-a2a net_position_boundsno single holding > 20.00 USDC
Capabilityacquire tool:[email protected] from registrywithin bounds
Payloadload sha256:c1a9…sealed from intake-42within bounds
Market · buydataset:market-ticks 12.50 USDC · settled against proof-of-deliverywithin bounds
Footprintspawn +2 sub-agentswithin bounds
Market · buycompute:gpu-hours 41.00 USDC — cumulative 53.50 would exceed cost_cap 50.00 · refused & signeddivergence
Market · sellinference-output:derived-summary 9.00 USDC · settled against proof-of-deliverywithin bounds
Footprintretire -2 sub-agentswithin bounds
Capabilityshed tool:[email protected]within bounds

timeline_merkle_root → bound_to_assembly_root · open the signed example (JSON) →

The binding is the point: at any step, a verifier can prove and answer — what was this agent capable of, what was it carrying, what had it bought or sold, and how big was it — at the moment it took that action. The agent’s economic life and its work are one verifiable object.

Mission-bounded economics — the guardrail that makes it safe to run

A self-trading agent that can buy and sell needs authorized bounds, or it’s a runaway. The operator authors an economic mandate; each market, capability, and footprint mutation is cleared against it before it executes. A mutation that would breach the mandate is either refused (signed refusal) or flagged as a signed divergence and escalated — the same mechanic as mission-coherence drift.

The operator sets the bounds. Hive applies and signs the result. Hive never sets the bounds and never judges the trades — it proves whether each mutation stayed inside the mandate the operator authored.

Anyone can prove the agent’s economic life — offline

The public verifier returns, alongside the computation graph, the metamorphosis timeline: the agent’s capability, payload, market, and footprint history. A third party reconstructs and verifies the entire economic-life history from receipts alone — with no trust in the agent, the operator, or Hive. Tamper with a mutation deep in the timeline, or reorder a buy/sell, and the binding verification fails. Each receipt is dual-signed — Ed25519 + ML-DSA-65 (post-quantum, FIPS 204).

Run it, route it, or prove it

Every path below is a real, reachable destination — no fake checkout, no invented prices.