Capital OS (/agent)
Capital OS is the orchestration layer that sits above the proof pipeline. Policy posture, vault constraints, and execution gates are all proof-backed — changes to execution policy require valid proof state before they take effect. This is not a dashboard for reading numbers; it is the control plane where a user's cryptographic trust posture determines what actions are available.
What You Use It For
- Manage capital posture and privacy-vault state.
- Check trust and gate readiness before placing risk.
- Configure guided/manual vs automation behavior.
- Hand off prepared context to Trade Desk for execution.
Workspace Map
Capital Ledger (left)
- Capital posture and vault state.
- Deposit/withdraw/privacy entry points.
- Commitment and dark-ledger related controls.
Operations (center)
- Mission-control workflows.
- Strategy and policy preparation.
- Execution handoff controls.
Control Plane (right)
- Health/readiness checks.
- Intelligence and risk signal panels.
- Fast status confirmation before trading.
Practical Workflow
- Connect wallet and complete onboarding prompts.
- Open
/profileand confirm trust/reputation readiness. - Return to
/agentand validate:
- capital posture
- policy/gate status
- health signals
- Choose operation mode:
- guided/manual for explicit control
- automation only after first validated cycle
- Hand off to Trade Desk for route selection and execution.
Operator Checks Before Handoff
- Trust/gating state is compatible with intended action.
- Capital posture is updated and not stale.
- No system health warnings in control plane.
Next: Trade Desk | How Systems Work | Profile And Identity