Manifestos
One affirmative claim — we wrote all of our software ourselves — defended by sixteen technical documents. Start with the thesis; two manifestos are available here, and the remaining fourteen are available on request.
The Build-Everything Thesis
The positive claim the sixteen manifestos defend, and the one economic change — the collapsing cost of writing correct code — that makes building everything rational rather than reckless. Includes the direct answer to the first objection: isn't your library a dependency too?
Read the thesis ->
Trust
You cannot audit code you did not write — whether it arrives as a package, a CVE, a SaaS contract, or a drive-by contribution.
The Anti-Dependency Manifesto
Modern applications can carry hundreds or thousands of transitive packages maintained outside the team that ships them. We eliminated that package graph. The bill of materials has four entries.
The Anti-CVE Manifesto
The National Vulnerability Database published over 33,000 CVEs in 2025. Our count from upstream dependencies is zero. Supply chain attacks only work if there's a supply chain.