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.
This blueprint defines Customer Ops response templates and SLA tiers without enabling customer contact, review closure, delegated authority, or department promotion.
Current truthSupport-only
Complaint Intake remains a support lane. Templates and SLA policy are not active customer-facing authority.
TemplatesDraft-only
Acknowledgement, missing-information, governed-review update, and resolution-ready summaries can be prepared for human review only.
SLA tiersBlueprint only
Standard, missing-information, governed-review, medical/essential-service, and legal/privacy risk tiers are visible but not enabled.
Human governorCustomer-facing approval
Sending responses, closing reviews, refund promises, escalations, and customer-facing commitments still require human approval.
Founder-onlyPolicy / thresholds
Customer-contact policy, SLA commitments, legal/privacy/medical posture, refunds, delegated thresholds, and promotion stay founder-level.
Next buildReview closure blueprint
Define closure rules and receipt proof next, still without enabling autonomous closure or customer contact.
This card does not contact customers, send responses, close reviews, promise refunds, change policy, write receipts, enable delegation, or promote Customer Ops.
This blueprint defines governed review closure rules and receipt proof without enabling customer contact, autonomous closure, delegated authority, or Customer Ops promotion.
Current truthHuman-governed
Review closure remains human-governed. AI may prepare packets but cannot close reviews or send customer-facing resolution.
Closure rulesBlueprint only
Source identity, risk escalation, human approval, and receipt proof are defined as rules, not active closure authority.
Receipt proofWrite path disabled
Closure receipt fields are visible for future policy review, but no receipt write or approval authority is enabled.
Human governorClosure approval
Closing reviews, customer updates, refund promises, and escalations still require human approval with source evidence.
Founder-onlyPolicy / liability
Legal, privacy, medical, refund, customer-contact, delegated thresholds, and promotion decisions stay founder-level.
Next buildSignals freshness watch
Move next to provider freshness and business-watch visibility without treating Signals drift as a launch blocker.
This card does not close reviews, contact customers, promise refunds, change policy, write receipts, enable delegation, 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.
This blueprint defines spend thresholds, escalation bands, and receipt proof for Finance without enabling spend approval, money movement, pricing changes, vendor commitments, or Finance promotion.
Current truthCandidate authority
Finance remains observation-only. Thresholds are visible for review but are not active approval authority.
ThresholdsBlueprint only
Zero-spend, low-spend, recurring-spend, provider/API spend, refund, vendor, and emergency bands are defined as review categories only.
AI labor nowRead / calculate / warn / draft
AI may calculate spend indicators, surface threshold warnings, and draft finance packets with source evidence.
Human governorApproval required
Any spend, refund promise, vendor commitment, pricing change, or threshold exception still requires human approval.
Founder-onlyMoney / pricing / vendors
Spend policy, pricing, capital allocation, vendor commitments, delegated thresholds, and Finance promotion stay founder-level.
Next buildRisk policy registry
Move next to compliance/risk policy registry blueprints before enabling any delegated operating authority.
This card does not move money, approve spend, change pricing, promise refunds, mutate providers, write receipts, enable delegation, 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.
This surface makes provider freshness, attribution thinness, and low-traffic Signals drift visible as business-autonomy watch truth without treating it as a launch-critical coverage gap.
Current truthProvider support-only
Signals may read provider truth and surface drift, but it does not hold provider mutation or department authority.
Watch scopeFreshness / attribution
Analytics, search, social, traffic freshness, source attribution, and conversion visibility are tracked as business-watch items.
Business impactGrowth readability
Low traffic, stale provider data, or thin attribution can reduce business autonomy confidence without blocking launch readiness.
Launch boundaryNot launch blocker
Signals freshness drift must not create coverage gaps, founder approvals, or runtime-gate failures while live L5 launch truth is green.
AI labor nowRead / warn / draft
AI may calculate indicators, surface warnings, and draft growth-readiness packets with source evidence only.
Founder-onlyCampaigns / spend / messaging
Provider mutation, campaign launch, growth spend, public messaging, tracking/privacy posture, and promotion stay founder-level.
This card does not mutate providers, launch campaigns, approve growth spend, publish messaging, contact customers, create launch blockers, 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.
This blueprint turns legal, medical, privacy, refund, customer-contact, public-messaging, and delegated-risk boundaries into visible policy objects without enabling policy changes or autonomous authority.
Current truthFounder-governed
Risk / Compliance remains human/founder governed. The registry is read-only and does not grant department authority.
Policy objectsBlueprint only
Privacy, legal, medical/essential-service, refund, customer-contact, public-message, and delegated-risk policies are defined for review only.
AI labor nowFlag / draft / route
AI may classify risk, draft policy packets, surface missing evidence, and prepare safe summaries for human review.
Human governorApproval required
Customer responses, review closure, risk exceptions, refund promises, and escalations still require human approval.
Founder-onlyPolicy / liability
Privacy, retention, legal, medical, refund, public messaging, delegated thresholds, and promotion stay founder-level.
Next buildReceipt-backed policies
Move from blueprint objects to source-backed policy receipts later, still without enabling writes or customer contact.
This card does not contact customers, close reviews, give final legal/medical/privacy decisions, change policy, write receipts, enable delegation, or promote Risk / Compliance.
This blueprint maps Risk / Compliance policy objects to source surfaces and proposed receipt proof without enabling policy changes, receipt writes, customer contact, review closure, delegated authority, or promotion.
Current truthFounder-governed
Policy packets can be prepared for review, but Risk / Compliance remains human/founder governed.
Source proofRequired before action
Each future packet needs policy object, source surfaces, allowed boundary, forbidden boundary, escalation state, and approval requirement.
Write pathDisabled
No policy receipt, approval receipt, closure receipt, or delegated-governor write is enabled by this packet.
AI labor nowMap / draft / escalate
AI may map policies to proof surfaces, draft internal packets, and surface missing evidence for human review.
Founder-onlyPolicy / liability
Policy text, privacy/retention, legal, medical, refund, public messaging, delegated thresholds, and promotion stay founder-level.
Next buildRead-only example receipt
Build the first source-backed policy packet example next, still without enabling receipt writes or customer contact.
This card does not contact customers, close reviews, give final legal/medical/privacy decisions, change policy, write receipts, enable delegation, mutate production, or promote any lane.
This example shows one source-backed Risk / Compliance policy receipt packet shape for human review without enabling receipt writes, policy changes, customer contact, review closure, delegated authority, production mutation, or promotion.
Current truthRead-only example
The packet is generated as JSON only. It is not stored as an approval, closure, policy, or delegated-governor receipt.
Example domainMedical / essential service
Demonstrates source mapping and escalation boundaries for a high-risk policy object without giving advice or contacting customers.
Source proofAttached routes
Links policy registry, receipt packet blueprint, customer integrity, governed reviews, and launch proof as read-only evidence surfaces.
Write pathDisabled
No policy receipt, approval receipt, closure receipt, or delegated-governor write is enabled by this example.
Human boundaryApproval required
Customer contact, review closure, policy changes, refunds, medical/legal/privacy decisions, and escalation commitments remain human/founder governed.
Next buildPolicy receipt templates
Move to governed policy receipt templates only after founder-approved policy text and write-boundary rules exist.
This card does not contact customers, close reviews, give final legal/medical/privacy decisions, change policy, write receipts, enable delegation, mutate production, or promote any lane.
This blueprint turns source-backed policy receipt examples into reusable policy receipt templates without enabling receipt writes, policy changes, customer contact, review closure, delegated authority, production mutation, or promotion.
Current truthTemplate-only
Templates can be reviewed as JSON, but they are not stored as approval, closure, policy, or delegated-governor receipts.
Template domainsRisk / privacy / money / messaging
Medical/essential-service, privacy/data, refund/compensation, and public-messaging templates are defined for human review only.
Write pathDisabled
No policy receipt, approval receipt, closure receipt, or delegated-governor receipt write is enabled by this blueprint.
AI labor nowMap / draft / surface gaps
AI may draft template fields, attach source surfaces, and surface missing founder-approved policy text for review.
Founder-onlyPolicy text / write rules
Policy language, privacy/retention, legal, medical, refund, public messaging, thresholds, and write-boundary approval stay founder-level.
Next buildPolicy text gate
Define the founder-approved policy-text gate and write-boundary rules next, still without enabling receipt writes or customer contact.
This card does not contact customers, close reviews, give final legal/medical/privacy decisions, change policy, write receipts, enable delegation, mutate production, or promote any lane.
This blueprint defines the founder-approved policy-text gate and receipt write-boundary rules required before any policy receipt template can become active. It remains read-only and does not enable policy changes, receipt writes, customer contact, review closure, delegated authority, production mutation, or promotion.
Current truthGate blueprint
The gate is visible for review only. It does not approve policy text, activate templates, or create receipt-write authority.
Policy textFounder-approved required
Every future policy template needs approved policy text, owner, source surfaces, retention posture, and risk domain before activation.
Write boundaryDisabled
No policy receipt, approval receipt, closure receipt, or delegated-governor write may occur until a governed write route is explicitly approved.
AI labor nowCompare / draft / surface gaps
AI may compare templates to source proof, draft internal gap packets, and surface missing founder-approved text for human review.
Human boundaryApproval required
Policy text, legal/privacy/medical posture, refund language, public messaging, threshold rules, and receipt-write enablement require human/founder approval.
Next buildPolicy approval packet draft
Prepare a read-only approval packet draft next, still without enabling writes, customer contact, policy changes, or delegation.
This card does not contact customers, close reviews, give final legal/medical/privacy decisions, change policy, approve policy text, write receipts, enable delegation, mutate production, or promote any lane.
This blueprint prepares a founder-review packet shape for policy text and write-boundary approval without approving policy text, enabling receipt writes, contacting customers, closing reviews, delegating authority, mutating production, or promoting any lane.
Current truthDraft-only
The packet can be prepared for review, but it is not an approval, receipt, policy change, or delegated-governor action.
Approval stateNot approved
Founder-approved policy text, write-boundary rules, and activation authority are still missing by design.
Packet contentsPolicy / source / boundary
Draft fields cover policy object, source surfaces, allowed boundary, forbidden boundary, escalation state, and approval requirement.
Write pathDisabled
No policy receipt, approval receipt, closure receipt, or delegated-governor write is enabled.
Human boundaryFounder approval required
Policy text, risk posture, refunds, public messaging, thresholds, customer contact, and receipt-write enablement remain human/founder governed.
Next buildFounder policy review checklist
Prepare the checklist next, still without approving policies, writing receipts, contacting customers, or enabling delegation.
This card does not contact customers, close reviews, give final legal/medical/privacy decisions, change policy, approve policy text, write receipts, enable delegation, mutate production, or promote any lane.
This blueprint converts the policy approval packet draft into a founder-review checklist without approving policy text, enabling receipt writes, contacting customers, closing reviews, delegating authority, mutating production, or promoting any lane.
Current truthChecklist-only
The checklist can structure founder review, but it is not an approval, policy change, receipt, or delegated-governor action.
Review itemsPolicy / risk / source / boundary
Founder review items cover policy text, risk domain, source proof, allowed boundary, forbidden boundary, escalation, and write authority.
Approval stateNot approved
Founder-approved policy text, activation authority, and receipt-write enablement remain missing by design.
Write pathDisabled
No policy receipt, approval receipt, closure receipt, or delegated-governor write is enabled by this checklist.
Human boundaryFounder decision required
Policy text, legal/privacy/medical posture, refunds, public messaging, thresholds, and receipt writes remain human/founder governed.
Next buildPolicy decision receipt blueprint
Prepare a decision-receipt shape next, still without writing receipts, approving policies, contacting customers, or enabling delegation.
This card does not contact customers, close reviews, give final legal/medical/privacy decisions, change policy, approve policy text, write receipts, enable delegation, mutate production, or promote any lane.
This blueprint defines a future founder decision receipt shape for policy approval outcomes without approving policy text, enabling receipt writes, contacting customers, closing reviews, delegating authority, mutating production, or promoting any lane.
Current truthBlueprint-only
The decision receipt can be reviewed as JSON, but it is not stored as an approval, policy, closure, or delegated-governor receipt.
Decision stateNot approved
Future states may include approved, rejected, needs-evidence, or escalated; this card does not make or record that decision.
Receipt fieldsPolicy / source / boundary / audit
Draft fields cover policy object, source surfaces, decision state, allowed boundary, forbidden boundary, escalation, reviewer, and audit index.
Write pathDisabled
No policy receipt, approval receipt, closure receipt, delegated-governor receipt, or production write is enabled.
Human boundaryFounder decision required
Policy text, legal/privacy/medical posture, refunds, public messaging, thresholds, and receipt-write enablement remain human/founder governed.
Next buildDecision receipt storage preflight
Prepare a storage preflight next, still without writing receipts, approving policies, contacting customers, or enabling delegation.
This card does not contact customers, close reviews, give final legal/medical/privacy decisions, change policy, approve policy text, write receipts, enable delegation, mutate production, or promote any lane.
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 packet turns the daily founder brief into source-backed operating proof: AI-done work, delegated-review candidates, founder-only decisions, and follow-up packets stay separated before any delegation is enabled.
Current truthPacket ready / read-only
The daily brief can be prepared and reviewed, but no acknowledgement receipt write or delegated-governor authority is enabled.
Brief sectionsLaunch / customer / money / growth / risk
Founder sees exception lanes and source surfaces instead of routine queue grind.
AI-done workPrepare / attach / route
AI may summarize status, attach proof routes, draft follow-up packets, and surface drift without external action.
Delegated reviewTemplate only
Acknowledgement receipt fields are defined, but no delegated governor can write approval receipts yet.
Founder-onlyDeploy / money / policy / liability
Promotion, production mutation, spend, legal/privacy/medical policy, public messaging, and threshold changes stay founder-level.
Next buildCustomer Ops templates
Move next to SLA/templates and review-closure policy blueprints without enabling customer contact.
This card does not approve, deploy, contact customers, mutate providers, move money, close reviews, publish messaging, change policy, write receipts, 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.