Overview / Actions & gates
BM
Direct · human approval surface

Action proposals

The VEO proposes — you decide, and you execute. This page is a human-only surface; it is never exposed as an agent tool.
paymentproduct always stop here — no exceptions, no executor
Payment Product Comms Research Memo
ProposalKindAmountWaitingExpected effectStatus

VEO tasks — its own to-do memory

7 in flight
🗂️
Triage 12 oldest MarketNinja review items
t-88 · in progress · labels proposed, human confirms on the review boards
Active
🏛️
Watch the entity filing → then propose bank + Stripe setup tasks
t-89 · blocked on gate a-141
Blocked
📋
Draft Sunday board-meeting agenda
t-87 · done · waiting in the boardroom
Done

How the gates hold

In codeActionProposal.Normalize()
In the databaseveo_force_approval trigger
Executor for gated actionsnone exists — by design
Connectorsread-only · a write anywhere = product
🛡️
Both layers stay. If they ever disagree, the database wins — a proposal can't be un-gated by a prompt, a bug, or the VEO itself.
payment gated — human only

File Clixion LLC — Texas SOS

a-141 · proposed by Direct, cycle #1,978 · Thu Jul 9, 21:04

{ "kind": "payment", "payee": "Texas Secretary of State", "amount": 308.10, "memo": "Clixion LLC certificate of formation + Bunkio DBA ($25)", "requires_approval": true // forced by Normalize() }
Why nowentity decided Jul 9 (see journal)
Unblocksbusiness banking · Stripe · DBA filings
Downside if deferredStripe onboarding slips ~2 weeks
ProvenanceMonitor saw the decision note → Direct proposed
VEO's case: every live workstream (Stripe for Bunkio, business bank for the flip bankroll, DBAs) queues behind this $308. Cheapest unblock on the board.
Approving records your decision — the VEO has no executor for gated actions. You file and pay; the VEO tracks the follow-through as tasks.