Active—
Workers active
Web Clicks—
Signal traffic
Complaints Submitted—
Complaint intake
Blocked—
Needs movement
Coverage Gap—
Non-active lanes
System vs Observed—
Continuity state
L5 means runtime truth and launch gates are green. L5 does not mean every lane has autonomous department authority.
Runtime L5Green runtime truth
Canonical system reality and launch gates can be green.
Candidate authorityNot promoted
Proof or readiness exists, but formal department authority has not been granted.
Verified proof laneEvidence exists
Evidence is visible and governed; this is not the same as autonomous authority.
Support-onlyPrepare / route / verify
BOA may support the lane but must not act as final department authority.
Provider support-onlyRead provider truth
BOA may surface provider readiness and drift without mutating providers.
Human boundaryApproval required
Deployment, production mutation, customer contact, review closure, and promotion require human approval.
BOA GPT is AI labor, not final authority. Green runtime is allowed. Candidate/support states are allowed. Hidden or unclear authority language is not allowed.
BOA is green for runtime and launch. The next business-readiness step is separating safe AI autonomous work, delegated human-governor work, and founder-only decisions.
AI autonomousObserve / prepare / verify
AI labor may run read-only checks, classify, summarize, draft packets, and surface drift without customer contact or production mutation.
AI prepares reviewApproval-ready packets
Patch zips, customer drafts, review packets, risk summaries, and handoff recommendations must include source evidence and boundary notes.
Delegated governorRoutine human approval
Bounded operational approvals can move out of founder hands only after a formal delegation policy and receipt path exist.
Founder-onlyVision / liability / capital
Department promotion, material deploys, legal/privacy risk, policy changes, spend thresholds, public messaging, and strategy stay founder-level.
Current autonomyYellow
BOA is controlled-production ready with founder oversight, but not yet low-grind business-autonomous ready.
Next build orderCustomer Ops → FIN → Signals → Risk
Promote business leverage by building operating spines, not by hiding candidate/support states.
This card does not approve, deploy, contact customers, mutate production, or promote any lane. It defines the delegation boundary needed for founder-level leverage.
Complaint Intake is live and useful, but it remains support-only until Customer Ops has templates, SLA tiers, delegated thresholds, resolution receipts, and promotion proof.
Current truthSupport-only
Complaint Intake may classify, prepare, queue, and route, but it is not final department authority.
AI labor nowDraft / route / verify
AI may prepare response drafts, review packets, Labs routing, and mismatch alerts with source evidence.
Human governorCustomer-facing approval
Review closure, response sending, refund promises, and escalations require human approval.
Founder-onlyPolicy / promotion
Refund policy, legal/privacy posture, medical handling, delegated thresholds, and department promotion stay founder-level.
Missing spineSLA + templates
Customer Ops needs governed templates, SLA tiers, escalation policy, and resolution receipts before promotion.
Next buildCustomer Ops proof pack
Build the operating spine first; do not promote by hiding support-only truth.
This card does not contact customers, close reviews, promise refunds, mutate production, or promote Customer Ops.
Finance is verified as a proof lane, but IRL business readiness needs revenue truth, spend truth, burn, runway, unit economics, and founder-approved spend thresholds.
Current truthCandidate authority
Finance remains observation-only. This surface does not promote Finance to department authority.
Visible metricsGross / net / spend
24h, week, and month finance fields are surfaced so zero-data and stale-data cannot hide.
Unit economicsCost per complaint
BOA should expose cost per complaint, cost per Labs run, provider spend, burn, and runway.
AI labor nowCalculate / warn / draft
AI may read finance truth, calculate visible indicators, surface warnings, and draft recommendations.
Founder-onlyBudget / pricing / spend
Spend thresholds, pricing, vendor commitments, capital allocation, and Finance promotion stay founder-level.
Next buildSpend ledger + brief
Build provider/API spend ledger, daily finance brief, thresholds, and recommendation receipts before promotion.
This card does not move money, approve spend, change pricing, promise refunds, mutate providers, or promote Finance.
Signals is verified as a provider lane, but IRL business readiness needs provider freshness, attribution, conversion quality, growth recommendations, and founder-approved campaign thresholds.
Current truthProvider support-only
Signals may read provider truth, but it does not hold provider mutation or department authority.
Visible metricsTraffic + intake
Website clicks, complaint submissions, incomplete intake, and conversion rate must stay visible.
Growth controlAttribution + quality
BOA needs source attribution, funnel stage quality, lead quality, and provider freshness before growth autonomy.
AI labor nowCalculate / warn / draft
AI may read signals, calculate conversion indicators, surface stale-data warnings, and draft recommendations.
Founder-onlyCampaigns / spend / messaging
Campaign launches, provider mutations, tracking/privacy posture, spend, and public messaging stay founder-level.
Next buildGrowth brief + receipts
Build provider freshness ledger, attribution map, weekly growth brief, and recommendation receipts before promotion.
This card does not mutate providers, launch campaigns, approve growth spend, publish messaging, contact customers, or promote Signals.
Risk and compliance are the boundary between useful AI labor and unsafe autonomy. Legal, medical, privacy, customer-contact, and policy decisions stay human/founder governed.
Current truthFounder-governed
BOA may prepare and route risk evidence, but it does not hold final legal, medical, privacy, or customer-contact authority.
Risk domainsLegal / medical / privacy
Legal threats, medical or essential-service complaints, data/privacy requests, refunds, and public claims need governed boundaries.
AI labor nowFlag / draft / route
AI may classify risk, prepare review packets, draft safe summaries, and surface missing policy or stale evidence.
Human governorCustomer-facing closure
Review closure, customer responses, refund promises, and escalations require human approval with receipt proof.
Founder-onlyPolicy / liability
Privacy, retention, legal posture, medical handling, delegated thresholds, public messaging, and promotion stay founder-level.
Next buildRisk policy registry
Build response templates, escalation playbooks, privacy/data paths, risk thresholds, and compliance receipts before autonomy.
This card does not contact customers, close reviews, give final legal/medical/privacy decisions, change policy, or promote Risk / Compliance.
BOA is green for controlled production. The next autonomy step is a daily brief that separates AI-done work, delegated-governor work, and founder-only decisions.
Current business truthAutonomy yellow
Runtime and launch are green, but low-grind business autonomy still needs operating receipts and thresholds.
AI may do nowRead / prepare / verify
AI may monitor, classify, calculate, draft packets, prepare patches, and surface drift without external action.
Delegated governorThresholds pending
Routine approvals can move out of founder hands only after approved thresholds, templates, and receipt paths exist.
Founder-onlyVision / liability / capital
Promotion, deploys, spend thresholds, policy, privacy/legal posture, public messaging, and strategy stay founder-level.
Daily brief shapeLaunch / customers / money / growth / risk
The founder should see exceptions and strategic choices, not routine queue grind.
Next buildBrief receipts + thresholds
Create receipt-backed daily briefs and delegated-governor thresholds before expanding autonomy.
This card does not approve, deploy, contact customers, mutate providers, move money, close reviews, publish messaging, or promote any lane.
This is the bridge from founder oversight to low-grind operations: define what can be delegated, what still escalates to founder-only authority, and what receipt proof is required.
Current truthDefined, not enabled
Threshold candidates are visible, but no delegated-governor authority is activated by this card.
Candidate lanesBrief / cleanup / routine review
Daily brief acknowledgement and low-risk internal cleanup are candidates; customer-contact and closure remain blocked until templates and receipts exist.
Receipt pathRequired before action
Every delegated approval needs actor, source surfaces, threshold basis, allowed boundary, forbidden boundary, and escalation state.
Founder-onlyPolicy / money / liability
Promotion, deploys, spend, legal/privacy/medical posture, public messaging, and threshold changes stay founder-level.
AI labor nowPrepare / score / escalate
AI may prepare threshold packets and fail closed when a request crosses customer, provider, spend, production, or policy boundaries.
Next buildTemplate + receipt store
Build customer templates, review-closure policy, spend thresholds, growth thresholds, and delegated-governor receipt storage.
This card does not approve, deploy, contact customers, mutate providers, move money, close reviews, publish messaging, change policy, or promote any lane.
Before routine work leaves the founder’s daily grind, every delegated-governor action needs source-backed receipt proof. This surface defines the receipt model without enabling delegation.
Current truthRead-only blueprint
No delegated-governor write path or approval authority is enabled by this card.
Receipt typesBrief / cleanup / review
Daily brief acknowledgement, internal cleanup, routine review, finance, and growth receipts are defined as candidates.
Required proofSource + boundary
Each future receipt must record actor, source surfaces, threshold basis, allowed boundary, forbidden boundary, and escalation state.
AI labor nowPrepare / score / attach
AI may prepare receipt packets and fail closed when customer, provider, spend, production, or policy boundaries are crossed.
Founder-onlyPromotion / deploy / spend / policy
Authority promotion, deploys, money, policy, privacy/legal/medical posture, public messaging, and threshold changes stay founder-level.
Next buildReceipt storage adapter
Build the actual receipt store, daily brief receipts, customer templates, review closure policy, and threshold receipts before enabling delegation.
This card does not approve, deploy, contact customers, mutate providers, move money, close reviews, publish messaging, change policy, write approval receipts, or promote any lane.
This surface defines the receipt-storage adapter contract needed before low-risk delegated governor receipts can be written. It does not enable delegation or receipt writes.
Current truthAdapter defined / disabled
The storage adapter is a read-only contract. No approval write authority is enabled.
Write pathDisabled fail-closed
Any missing source, stale threshold, customer, provider, spend, production, policy, or legal/privacy/medical boundary escalates instead of writing.
Storage modelAppend-only receipts
Future receipts need idempotent IDs, source surfaces, allowed and forbidden boundaries, escalation state, and audit index entries.
PII / retentionMinimize before write
Receipt storage requires founder-approved privacy, retention, and source-reference policy before enablement.
Founder-onlyEnablement / thresholds
Receipt-write enablement, threshold changes, policy, money, deploys, customer contact, and promotion stay founder-level.
Next buildDaily brief receipt packet
Build receipt packets and templates first; do not enable delegated writes until the adapter is approved and witnessed.
This card does not approve, deploy, contact customers, mutate providers, move money, close reviews, publish messaging, change policy, write approval receipts, or promote any lane.