Web4Guru AI Operations
Home · Docs · Core Concepts

Core Concepts

Fifteen short pages that explain how Black Box thinks. Read the first four for the shape; use the rest as reference when a specific thing surprises you.

Start with the AI company model Getting Started

What you'll learn

  • Why Black Box is an AI company, not an AI assistant.
  • How the CEO agent decides what to do next.
  • What the 18 specialists actually do, and how delegation works.
  • How the product protects your credits, vets its own work, and remembers your business.
  • How autonomy, playbooks, skill packs, and connections compose into outcomes.

Read in order, or jump around

Concepts 1–4 are the spine — they explain the shape of the product. Concepts 5–8 cover the surfaces you actually interact with (playbooks, skill packs, the four views, the seven card types). Concepts 9–15 are the deeper machinery — safety, memory, autonomy, the meta-loop, the credit system, and connections.

1 The AI company model What "AI company" means and why the framing matters. 2 The CEO agent Role, decision loop, limits. 3 The 18 specialists Who they are and what they do. 4 Delegation How the CEO picks a specialist and hands over the work. 5 Skill packs Vertical expertise you install on top of the core team. 6 Playbooks Pre-wired sequences for common outcomes. 7 The four views Boardroom, Power Grid, Action Feed, Approvals Inbox. 8 Structured cards The seven bb_event types the owner actually sees. 9 The Evaluator gate Why every deliverable is reviewed before it reaches you. 10 The circuit breaker Five safety-halt reasons that protect your credits. 11 Company memory How Black Box remembers your business across sessions. 12 Autonomy levels When the team acts alone vs asks for approval. 13 The meta-loop How the product learns from how builders build it. 14 The credit system How usage translates to credits. 15 Connections How Black Box connects to your other tools.

Frequently asked

Do I need to read all fifteen?
No. Read concepts 1–4 for the shape. Use the rest as reference.
How is this different from Getting Started?
Getting Started ships your first outcome. Core Concepts explains the why.
Do I need to be a developer?
No. Owner-first explanations, with a nod to the mechanism where it helps.

Further reading