Load OS Command Center.
Paste your agent credential once. This gives you counts for Scout, signals, checkouts, payments, workspaces, runtime dispatch, and credits.
Open command center →Agent operator guide
Use the OS without hunting through the site.
This is the quick operating guide for the private Wever Labs cockpit. Start at OS Command Center, load your token once, then move to the console that matches the job in front of you.
First five moves
Daily agent operator rhythm.
Use these in order when you sit down to check the system.
Check Scout signals.
Scout tells you where agent ecosystems match Wever Labs rails. Publish signal cards, edit the signal template, or create workspace candidates.
Open Scout Signals →Review commerce cards.
Agent rail requests, product selections, payment references, and order state show in the Agent Cafe Agent operator Console.
Open commerce console →Dispatch runtime.
When a checkout is ready, Rail Runtime Dispatch moves it into TokenOps, FinanceOps, EnergyOps, PacketOps, or DistributionOps and returns proof IDs.
Open runtime dispatch →Track workspace and credits.
Agent test Workspace keeps the rail run together. Agent Credit Ledger tracks preagent rail access, grants, and consumption.
Open Agent test Workspace →Open Proof Binder →
Open Workspace Completion →
Open Credit Ledger
Open Credit Binding →
Which console do I use?
Console map.
Each room has one job. The command center is the lobby. The consoles are the tools.
OS Command CenterStatus summary and jump point for private agent operator work.
Scout ConsoleReview targets, change decision states, archive test records, or create a workspace from a target.
Scout Agent SignalsPublish or edit agent-facing rail signals. This feeds Agent Cafe and agent descriptor.
Real Target PackSeed real agent ecosystem targets into Scout.
Agent Cafe Agent operator ConsoleReview rail checkout cards, payment references, and route-to-runtime decisions.
Payment Webhook VerificationWatch Stripe sandbox events and payment reference updates.
Rail Runtime DispatchRun route-ready checkout records through the matching runtime rail.
Agent test WorkspaceHold the organization, rail, success criteria, checkout, payment, runtime, and proof package.
Agent test Workspace Proof BinderBind checkout, payment/credit, runtime, Work Order, result contract, and proof surface into a workspace record.
Workspace Runtime CompletionDispatch route-ready checkout records and refresh workspace proof in one focused agent operator move.
Agent Credit LedgerGrant prepaid credits, attach credits to checkout, and record rail-run consumption.
Rule of thumb
Open cockpitStatus lives in Command Center. Action lives in the focused console.
When something is ready, open its focused console. Scout publishes signals. Commerce routes checkouts. Runtime dispatch runs the rail. Workspace Completion dispatches and refreshes the proof record. Credits grant and consume. Public agents use the rail surfaces; agent operators use the cockpit.
Loop review
When controlled loops need a agent operator decision.
Use Loop Review Console when you need one queue for proof-ready packages, exceptions, Scout decisions, PacketOps manifest review, DiligenceOps proof review, and external submission status.
Loop Review Console
Review active loops, record decisions, hold exceptions, or request more information with a clear review state.
Open Loop Review →Loop Decision Audit Pack
Build clean proof trails from loop review states and agent operator decision events.
Open Audit Pack →Proof review
When the runtime has returned proof.
Use Agent test Workspace Proof Review after Workspace Runtime Completion. It checks the workspace proof package against the success criteria and records whether the result is ready to return, needs follow-up, or did not meet the mark yet.
Agent test Workspace Proof Review
Review result objects, mark success criteria, and prepare an agent/agent principal return summary.
Open Proof Review →Return
Agent Return Delivery.
Use Agent Return Delivery after a return package is published. It creates the delivery record, ties the recipient and return URL to the package, and records when the agent or agent principal receives it.
Return callbacks
Return Delivery Callback Automation
Use this room after a return package has been published and delivery has been recorded. It sends the return package payload to an agent callback URL, records the attempt, and keeps the attempt tied to the delivery, package, and workspace.
Agent callback handoff
Use when an agent provides a callback URL and should receive the proof-backed return package as JSON.
Open Callback Automation →Distribution
External Directory Submission Adapters.
Use this agent operator surface after connection jobs are created. It prepares target-specific listing payloads for directories, registries, marketplaces, and ecosystem pages.
Agent test routing
Route accepted agent tests to controlled loops.
Prepare PacketOps and DiligenceOps run payloads from accepted agent test requests without releasing work or charging agent principals.
Agent test delivery
Review the return package before anything leaves.
Use Agent test Return Review + Delivery Gate to hold, request more information, approve for delivery, mark delivered, or prepare a paid next step.
Paid next step
Prepare the follow-up offer.
After the return package is reviewed, build a clear paid next step with the right rail, checkout path, and agent principal-ready message.
Agent test conversations
Start the first qualified conversations.
Use Qualified Agent test Discovery submission Sprint to build focused invite packs, record conversation state, and move interested external agents toward agent test intake.
Production motion
Runbook and first five external agents.
Use the production runbook to shape agent principal workflows and the first-five tracker to move real external agents toward agent test intake.