/the-product
The Product
The product is a control plane, not a chat window.
From a Meadows-style system perspective, Lightbulb is an attempt to redesign the feedback loops of company operations: sensing, interpreting, deciding, approving, executing, and learning.
System design view
| System concept | Lightbulb interpretation |
|---|---|
| Stock | Organizational context: documents, conversations, tasks, CRM records, finance data, projects, approvals, and institutional memory |
| Flow | Agentic work: signals enter Mission Control, pass through Backbone and Orchestrator, then route to domain agents and human approval |
| Feedback | Human judgment: approve, reject, modify, trace reasoning, and improve future recommendations |
| Rules | Approval boundaries, permissions, Shadow Mode, audit requirements, domain access |
| Leverage point | Changing information flows and decision rules, not merely adding more agents |
Architecture narrative
| Layer | Product language | Strategic meaning |
|---|---|---|
| Surface | Mission Control | The central feed where decisions, alerts, approvals, and actions become visible |
| Kernel | Backbone | Intent routing, memory, reasoning traces, and workspace handoffs |
| Scheduler | Orchestrator | Coordinates multi-step work across domains, tools, approvals, evidence, and telemetry |
| Executive loop | AutoCompany | Cross-domain operating council over authorized business domains |
| Context | Projects | Persistent delivery records connecting goals, repos, docs, artifacts, and execution |
| Applications | Domain workspaces | Finance, CRM, Legal, Engineering, Commerce, HR, Docs, Customer Success, Procurement, GRC, Solver, SmartSpaces |
Product claim requiring Robbie validation
The product should be described externally only after Robbie marks each claim as built, partially built, in progress, planned, vision, or do not disclose.