Private planner boundary
Hidden task inputs remain private and affect the execution path.
QueueKeeper keeps the product story concrete, then shows which protocol or sponsor rail is doing real work at each step.
These are the load-bearing parts of the main scout-and-hold loop.
Hidden task inputs remain private and affect the execution path.
Acceptance and reveal stay blocked until runner verification succeeds.
Explorer-linked staged micropayment contracts anchor the onchain happy path.
Spend cap, expiry, contract, and token limits remain visible in the happy path.
The agent is a first-class product actor, not a hidden implementation detail.
Agent identity, logs, and spend boundaries are surfaced in-product.
Identity surfaces can resolve ENS names with clean short-address fallback.
These tools are real, but they stay secondary to the core bounded-trust loop.
Uniswap API credentials are configured; live swap execution is the remaining step.
The paid venue-hint sidecar is live; recording a paid receipt is the remaining demo step.
Staged commitments, receipts, and proof-linked transitions map cleanly onto obligation semantics.