Company foundation
Corporate entitiesGovernanceObligationsFinances
Company as Code
The operating system that runs your company.
A founder defines intent, strategy, judgment, relationships, taste, risk tolerance, and authority. My Business organizes the company, coordinates agents, workflows, and software, and keeps authorized work moving.
Northstar, Inc.
Company operating graph
Intent
Launch a considered product line
Authority
Spend under $500 · L3
Work
17 active operating threads
Memory
Decision trail current
Authorized capability mixSoftware · agents · professionals
Company first. Work and outcomes belong to the company, not to a role or headcount plan.
Authority explicit. Every action carries an owner, boundary, approval path, and verification rule.
Memory preserved. The act of operating continuously creates evidence and institutional context.
The Company Graph
One model of what the company is and how it operates.
The Company Graph is the canonical model for the company’s legal reality, commitments, relationships, work, resources, decisions, and evidence. It makes coordinated action possible without making any actor the center of the system.
Operating context
CustomersKnowledgePoliciesDecisions
Execution layer
WorkflowsSoftwareAssetsVendors & providers
Control & memory
PermissionsEventsEvidenceInstitutional memory
Actors, not the architecture
The company chooses the right capability for the work.
Humans, agents, software, services and providers, and external professionals are actors and capabilities within the company. They receive bounded responsibilities from the Company Graph; none is the product’s organizing principle.
Humans
Founder judgment, relationships, decisions, and accountable authority.
Agents
Persistent functional operators that plan, act, escalate, and learn.
Software
Deterministic systems, workflows, interfaces, and integrations.
Services & professionals
Providers, vendors, accountants, counsel, and specialized expertise.
Operating loop
From founder intent to verified company memory.
01
Intent
The founder defines objectives, strategy, taste, risk tolerance, relationships, and authority.
02
Plan
The system decomposes intent into work, dependencies, policies, and desired outcomes.
03
Route
It selects deterministic software, an agent, a human, or an external professional for each action.
04
Authorize
Explicit authority boundaries determine what can proceed, what needs approval, and what is prohibited.
05
Execute
Agents, workflows, software, and people coordinate work across the company.
06
Verify & remember
Outcomes are checked; evidence, decisions, and operating context become company memory.
Intent → decompose / plan → determine deterministic software vs. agent vs. human / professional → authorize → execute → verify → record evidence / memory → monitor / learn.
Start with one founder
A one-person company can operate like a company.
A founder sets the direction and authority boundaries. The Company Graph coordinates a functional operating company across disciplines—without pretending every responsibility needs a full-time employee.
01
Marketing
Bounded by company policy and founder authority.
02
Sales operations
Bounded by company policy and founder authority.
03
Research
Bounded by company policy and founder authority.
04
Customer operations
Bounded by company policy and founder authority.
05
IT & administration
Bounded by company policy and founder authority.
06
Finance operations
Bounded by company policy and founder authority.
07
Knowledge
Bounded by company policy and founder authority.
08
Software generation
Bounded by company policy and founder authority.
Provider-agnostic execution
Own the company’s intent. Choose providers for execution.
Identity, email, calendar, documents, storage, automation, AI, and other capabilities remain abstract in the model. Google is provider #1 for early execution—not the architecture.
Build the capability, not another dependency.
Use native company capability when it exists, build or automate it where safe, then reach for a provider only when it earns its place.
Company as Code
Define what the company should accomplish. Let the system run it.
Organize the company, execute within defined authority, verify the outcomes, remember what happened, and keep moving.
Questions