Capital OS

STARKNET SEPOLIA ONLY

Capital OS is the full-feature version of the app — currently live on Starknet Sepolia, coming to mainnet. For the mainnet MVP, see Portfolio Rebalancer and Reputation Passport.

Capital OS is the workspace at /agent. It's where you manage capital posture, deploy into protocols, and control automation. Capital OS and Trade Desk are the same product — two surfaces of the same underlying proof-gated execution system. Capital OS is where you plan, monitor, and set constraints; Trade Desk is where you execute.

Everything here is proof-backed — changing vault policy requires valid proof state, deploying capital goes through the proof pipeline, and automation is bounded by session keys. The UI surfaces reflect your trust context, so what you see depends on your reputation tier and gate readiness.

Three surfaces, one workspace

/agent is split into three surfaces via the ?v= parameter. Think of them as three different lenses on the same underlying system:

Surface	URL	What it's for
Vault	/agent?v=vault	Capital posture — portfolio, deploy, yield, lending, staking, ledger
Oracle	/agent?v=oracle	Market intelligence — opportunity signals, risk radar, analytics
Brain	/agent?v=brain	Automation — agent controls, model config, pipeline status

Each surface has sub-views via &sub=. For example, /agent?v=vault&sub=trade drops you into the vault's trading context, and /agent?v=brain&sub=pipeline shows the proof pipeline's status.

flowchart TB
  Agent["/agent"]
  
  Vault["<b>Vault</b><br/>portfolio · yield · trade<br/>lending · staking · activity"]
  Oracle["<b>Oracle</b><br/>signals · radar · genome"]
  Brain["<b>Brain</b><br/>agent · models · pipeline · agents"]

  Agent -->|"?v=vault"| Vault
  Agent -->|"?v=oracle"| Oracle
  Agent -->|"?v=brain"| Brain

Vault: where capital lives

The Vault surface is where you look at your actual money. Portfolio state, deployment controls, yield views, and the ledger all live here.

When you first open it, you'll see your aggregate capital posture — balances across protocols, pending operations, health indicators. If there are warnings (low collateral, pending reconciliation, gate issues), they surface here before blocking you downstream.

The key operations:

• Deploy — allocate capital to a protocol. Goes through the full orchestration flow with simulation and wallet signing.
• Yield — view projected and realized yield across positions. Informs rebalancing decisions.
• Lending — collateral health, borrow capacity, credit eligibility. Reputation-driven — your FICO-pack proofs affect what you can borrow.
• Staking — protocol staking positions and rewards.
• Activity — ledger history. Every action that went through the system shows up here with receipts.

Oracle: where signals come from

The Oracle surface is market intelligence — separated from execution on purpose. The idea is that you should be able to look at opportunities, risk assessments, and analytics without accidentally triggering an execution flow.

• Signals — opportunity feed, filtered by relevance and risk profile
• Radar — risk indicators across pools and protocols
• Genome — deeper analytics and model-driven insights

When you find something interesting in Oracle, you hand off to v=vault&sub=trade for execution. The signal context carries over.

Brain: where automation is controlled

The Brain surface is the control plane for autonomous operation. It's where you grant session keys, configure automation constraints, and monitor what the agent is doing.

• Agent — lifecycle controls. Start, stop, pause, resume.
• Models — model composition and configuration. Which zkML models are active, what thresholds they use.
• Pipeline — proof pipeline observability. See what's proving, what's settled, what's stuck.
• Agents — registry of available agent configurations.

The critical thing about Brain: it doesn't bypass proof-gating. Starting autonomous mode still requires proof-backed validation for every action the agent takes. Brain is the steering wheel, not an override.

Typical workflow

1. Connect wallet and check /profile?tab=trust for gate readiness
2. Open Vault — verify capital posture, check health signals
3. Check Oracle — browse opportunities, assess risk context
4. Execute via Trade Desk or Vault deploy controls
5. Monitor in Brain if using automated modes
6. Return to Vault to verify receipts and updated posture

Legacy tab migration

If you're coming from the old dashboard UI, here's where everything moved:

Old URL	New URL
?tab=dashboard, ?tab=pools, ?tab=deploy	?v=vault
?tab=markets, ?v=trade	?v=oracle
?tab=dex, ?tab=swap, ?tab=lp, ?tab=limits	?v=vault&sub=trade
?tab=staking	?v=vault&sub=staking
?tab=agent, ?tab=models, ?tab=pipeline	?v=brain

The old ?tab= links still remap for backward compatibility, but don't use them in new integrations — they'll be removed eventually.