An operating system, not a bag of scripts.
Everything on this site (the research waves, the market intelligence, the shipped software, the outbound machine) runs on one personal operating system: composable capabilities that fan out in parallel and pass through gates that do not negotiate.
What a team gets is range and reliability in the same hire: one operator covering research, build, and go-to-market, on machinery that holds the line.
I'm not a software engineer. I'm an operator who builds working systems with AI.
The primitive foundation
Around sixty composable capabilities, grouped into six domains. Each is a small, sharp tool; the leverage is in composing them: the same primitives that researched this market also shipped this site.
Research & Intelligence
12- Parallel Research Wave
- Market Pulse Monitor
- Source Crawlers (web, social, email, feeds)
- Repo Explorer
Building & Shipping
11- App Build Orchestrator
- Spec Writer
- Plan Writer
- Design Consultation
- Code Review Gate
- Browser QA Loop
- Security Scan
- App Scaffolder
Knowledge & Memory
10- Knowledge Base
- Identity & Goals Layer
- Self-Improvement Loop
Operations
9- Session Lifecycle
- Task & Project Queue
- Structural Validators
Coordination
9- Cross-Project Messaging
- Parallel Agent Waves
- Sub-Agent Authoring
Documents & Delivery
9- Long-Form Drafting Pipeline
- Document Compression
- PDF/Doc Publishing
Why it holds
Range without reliability is a bag of scripts. Three structural ideas make this system trustworthy.
One orchestrator, many scoped specialists
Big jobs are decomposed by a single coordinating agent and fanned out to scoped specialists running in parallel, each with its own narrow brief, then synthesized back into one answer. The same pattern powers both the research waves and the software builds.
- A real research wave: one plan fanned out to 8 parallel investigators
- 174 deduplicated sources reconciled into a single synthesis
- Typical waves run 4–10 specialists at once
- spec
- plan
- build ⇄ review
- QA
- security
- ship
- privacy floorshipped surfaces clean
- type-checktsc · 0 errors
- tests30/30 passed
- production build25/25 pages
- commit lands on mainb343fa9 · verified
A rule in a prompt drifts; a hook holds
The non-negotiables are enforced by machinery, not memory: destructive commands blocked, protected files locked, database security required on every change, and a done-gate that runs type-check, tests, and a production build before any work may call itself finished. Honest status is part of the contract: blocked is a valid answer; forced-green is forbidden.
- Every feature runs spec → plan → build ⇄ review → QA → security → ship, each phase gated on a durable artifact
- The done-gate: type-check · tests · production build. Pass or it is not done
Every correction becomes a durable rule
When a run goes wrong, or a preference lands, the correction is written back into the system as a rule the next run inherits. The operation compounds instead of repeating its mistakes.
- The cycle: correction → captured rule → re-applied on the next run
- Build sessions end by folding what was learned back into the system that ran them
See it doing real work
The map above is the system in the abstract. These pages show it doing real work.