Living Guide
The full current AutoBuilder operating guide.
Living System Map
Noaerth Mode
Internal portfolio proving ground
AutoBuilder Mode
Self-improvement engine
Public User Mode
Controlled workspaces & plan gates
All modes share one controlled engine
System Map
Current executive thesis
AutoBuilder is a venture factory with a proprietary operating system. Noaerth dogfoods the strongest internal version. Users get controlled workspaces. The moat is workflow, not models.
What AutoBuilder is now
A dual-use engine: internal portfolio tool, self-improvement system, and public trial-to-paid product.
- Trial startup pages for free users
- Venture genome JSON
- Planned native build engine
- Worker factory on Hetzner
What AutoBuilder must not become
Avoid these failure modes:
- An AI wrapper with no owned workflow
- Cursor/Aider production dependency
- Free repo execution
- Public recipe exposure
- 1000 always-on workers
Core product architecture
Three modes share one controlled engine:
- Noaerth internal mode
- AutoBuilder self-improvement mode
- Public user mode with plan gates
Proprietary moat architecture
Venture Genome, Recipe Vault, Execution Graph, Agent Protocol, Quality Gates, Claim Registry.
- Expose results, not recipes
- Models are replaceable
Internal Noaerth mode
Portfolio scans, health scoring, patch plans—with approval for risky actions.
AutoBuilder self-improvement mode
Users → patterns → support/analytics → improvement tasks → approved fixes.
Public user mode
Free: trial page proof. Paid: deeper reports, repo workers, team tools.
Free trial startup page system
/start → genome → /trial/[slug] → share → feedback → credits → upgrade.
Paid build system
Unlocks repo-aware triage, technical briefs, repair plans, worker runs.
Native build engine
read → plan → patch → test → repair → report → approve → remember
Worker and queue system
Many logical agents, limited active workers, priority lanes P0–P5.
Support automation layer
Self-fix cards, docs, ticket summaries, product feedback loop.
Data, memory, and learning layer
Usage events, patterns, recipe evolution—private to operator.
Public/private boundary
Users see their results. Operator keeps recipes, rubrics, routing.
Approval gates
Push, deploy, email, billing, delete, expensive jobs—all require approval.
Infrastructure plan
Vercel (edge), Supabase (data), Hetzner (workers), Redis (queue).
Database objects
workspaces, startup_pages, venture_genomes, usage_events, credits, referrals.
Dashboards
Admin usage, Noaerth portfolio, support handoff, approval queue.
Build phases
Phase 1: trial funnel. Phase 2: native engine MVP. Phase 3: worker factory maturity.
Current highest-priority roadmap
See /roadmap — next 7 days focused on schema, intake, trial renderer, credits.
What not to build yet
K8s, 1000 workers, full IDE, marketplace, free repo execution, autonomous deploys.
Risks and controls
See /security and risk matrix on homepage.
Open decisions
See /open-decisions for pending choices and recommended defaults.
Next 7 days
Day-by-day plan in /roadmap.
Next 30 days
Native engine MVP, worker factory v1, paid tier unlocks.
Decision log
See /decision-log for confirmed decisions.
Living guide update rules
Update when: strategy shifts, major ship, new locked decision, or quarterly review.
- Bump version in prompt vault
- Sync decision log
- Refresh roadmap phases
Final compressed operating doctrine
AutoBuilder is the factory. Noaerth uses the strongest version. Self-improvement compounds. Users get controlled workspaces. Free = proof. Paid = execution. Private recipes stay private. Every risky action needs approval.