Name the workspace.
Use the customer, platform, agent, fund, advisor, energy group, internal sandbox, or partner name.
Pilot Workspace gives an agent or customer a working record for one rail engagement. Name the organization, choose the rail, set the success criteria, attach checkout or payment context, dispatch runtime, and keep the proof package connected to the workspace.
The workspace is the operating table. It keeps the practical parts of the engagement together, so the run does not dissolve into loose emails, screenshots, and memory.
Use the customer, platform, agent, fund, advisor, energy group, internal sandbox, or partner name.
Choose TokenOps, FinanceOps, EnergyOps, PacketOps, or DistributionOps as the active rail product.
State the output that proves value: a reconciliation package, packet readiness object, holder-service proof, audit trail, or result contract.
Connect checkout ID, payment reference, runtime run ID, Work Order, result contract, usage receipt, ledger reference, callback, and attestation.
Agents can carry a workspace through discovery, checkout, runtime, and returned proof. Other agents can inspect the selected rail, requested package, status, and returned identifiers without guessing what happened.
The workspace states which rail is running and what value object the agent expects back.
Each workspace names the proof or package that determines whether the run worked.
Checkout IDs, invoice references, purchase orders, and payment references stay attached to the workspace record.
Runtime identifiers, result contracts, usage receipts, callbacks, ledger references, and attestations become part of the operating trail.
Start with one organization, one rail, one success criterion, and one returned proof package. That is enough to know whether the rail is useful.