The mandate
Turn the founding idea into a company others can inspect and operate.
Turns an idea into a company blueprint, business documents, specialist plans, approvals, and a first operating cycle.
The Company Agent keeps the thesis, evidence, decisions, specialist work, and approval gates in one living source of truth. It is responsible for coherence across the company, not for pretending every founding question is already settled.
What to bring
Bring the idea before it has been polished into certainty.
The strongest brief names the first customer, the proposed business model, the proof you need next, and the assumptions you are least comfortable making.
- 01
Company name, idea, primary customer, business type, and stage
- 02
Goals, constraints, jurisdictions, preferred channels, and budget
- 03
Founder assumptions that still need evidence or a decision
- 04
The project where approved plans and todos should be applied
What you receive
A company foundation that can survive handoffs.
The result connects the readable business plan to a structured blueprint, an owned todo graph, and bounded briefs for every specialist.
- 01
Company blueprint
company/plan/company-blueprint.jsonReady when
Mission, principles, workstreams, milestones, dependencies, and approval gates are schema-valid.
- 02
Business plan
company/plan/business-plan.mdReady when
Customer, goals, evidence, assumptions, and decisions remain readable and reviewable by people.
- 03
Operating todo graph
company/operations/todos.jsonReady when
Every task has an owner, effect class, dependency, and acceptance evidence.
- 04
Specialist briefs
company/plan/company-blueprint.jsonReady when
Each subagent receives bounded context and a decision-relevant objective.
The method
Build the source of truth, then let specialists challenge it.
Company formation is treated as a dependency-aware program: evidence first, specialist plans second, approval-gated execution last.
- 1
Normalize
Separate the founder’s inputs into facts, hypotheses, constraints, decisions, and unanswered questions.
- 2
Test
Rank the assumptions that can most quickly change the company thesis or first milestone.
- 3
Delegate
Issue role-specific briefs in dependency order and preserve each specialist’s evidence.
- 4
Govern
Reconcile the plans, expose conflicts, and stop external effects at explicit approval gates.
Signals & guardrails
A coherent plan is useful only while uncertainty stays visible.
Progress is measured by resolved decisions and accepted evidence. Hidden assumptions, unowned dependencies, or premature execution are reasons to stop.
Signs the work is useful
- Critical assumptions with evidence
- Milestones with accepted evidence
- Approval gates still unresolved
Reasons to pause
- A hypothesis is silently promoted to fact
- External work starts before its exact action is approved
Approval boundary
Repository mutation · Deployment · External publishing · Spend · Legal acceptance
Technical appendix
The exact contract behind the profile.
Useful for operators who need to inspect the immutable Kit version, typed boundary, and verification surface.
- Kit
- company-suite@0.1.0
- Entrypoint
- create-company
- Function
- compile-company-foundation
- Runtime
- python@3.12
- Input
- company-intake.schema.json
- Output
- company-blueprint.schema.json
Verification
company-foundation-ready · business-plan-quality · legal-review-required · company-blueprint-schema
Connected systems
Adios Git · Adios Workspace · Adios Deployments