The Engine Room — the company that runs itself
SecuraCV is operated by one human, GitHub, and Claude — the rest is systems. Every fact has exactly one source, every page you see is generated from it, and a human only shows up when a system raises its hand. This page is the public window into that machinery. None of it is secret; all of it is in the repos.
This is not the Lab. The Lab shows what the devices do — flash one, watch it sign claims. The Engine Room shows what the company does: how parts stay priced, docs stay true, and nothing rots while nobody is watching.
The doctrine
Five rules, borrowed from the systems that do this best — distributors whose one canonical catalog feeds every surface, and design tools where supply-chain facts attach to parts by machine, never by hand. The full constitution lives in the repo: 20-self-running-company.md.
One canonical source per fact
A part number, a price, a pin map — each lives in exactly one file. Every table and total you see anywhere is generated from it, so no two surfaces can ever disagree.
Facts are fetched, never typed
Anything the outside world knows better — distributor stock, prices, lifecycle — is pulled nightly by code and stamped with provenance. A human typing a price is a bug.
Drift is a red X, not a habit
Every generated artifact is regenerated and diffed in CI; every hand-written schema has a lint. Stale data fails the build instead of quietly shipping.
Exceptions summon humans — schedules never do
No weekly reviews, no dashboards to remember. When a part goes out of stock or a price jumps, a system opens a GitHub issue. Silence means healthy.
The company fits in a context window
Every runbook and policy is written so an AI operator can execute it from the repo alone — exact commands, exact paths, explicit pass/fail. That's what makes “one person + Claude” real.
The system map
Every function of the company, the system that runs it, and its state. Each one links to the real code and the real CI runs — watch them fire.
Parts & sourcing — the BOM pipeline
running nightly
Humans state design intent in bom_*.csv (what part,
how many, required or optional). Every night
bom_pricing.py asks Digi-Key and Mouser for verified
SKUs, live stock, price breaks and lifecycle, snapshots them into
pricing.json, and regenerates the Build-it tables.
Out-of-stock, a >15% price move, or a part leaving production
opens an issue automatically. The Build-it page's
Order the parts panel turns any build into a
distributor-ready list — copy, paste, and the cart prices
itself, no account needed.
Hardware data — enclosures, options, firmware flags
drift-gated
The parametric OpenSCAD sources, the BOM CSVs and the firmware's
own config.h flags are parsed into one catalog; CI
re-renders and re-parses on every change and fails if any page
went stale. A renamed part can't silently lie on the website.
Software supply chain
per releaseA CycloneDX software bill of materials — the Rust kernel, the Node tools, the ESP32 firmware stack — is generated in CI for every release. What's inside the code is as auditable as what's inside the case.
Documentation integrity
every PREvery doc must be reachable from the index and every link must resolve — enforced by lint, so “add the doc, skip the map” is a red X instead of a habit. This website's claims are pinned by anti-rot fact tests against the real firmware and kernel.
Storefront
preview by design
One file — store.json — is the whole catalog: kits,
bundles, prices, batch caps. The store page renders it directly;
going live is Stripe Payment Links with zero fixed cost and no
tracking. Next: a margin guard that compares kit prices against
the nightly parts snapshot and flags drift automatically.
Fulfillment
systemized · human handsPrinting, flashing, kitting and shipping are physical — a weekly batch evening, run from a written procedure with the flashing jig and label pipeline doing the repetitive parts. Systemized, not yet system-executed. Atoms are the last mile.
Margin guard — parts cost vs. kit price
running nightly
Every price in store.json carries a cost recipe;
every night the guard joins it against the parts snapshot and
computes the margin behind every number on the store page.
Sinks under the floor → an issue with the three honest options:
reprice, re-source, or lower the floor on the record. Editing a
price in a PR runs the same judgement as a red-X check.
The operator loop
How anything gets done here — from “a part went end-of-life” to “fixed, verified, forgotten”:
What deliberately stays human
Self-running is not hands-off. Four things are never delegated to automation:
- Money movement. Systems prepare carts and quotes; a human clicks buy. No machine spends money here.
- Safety-critical choices. Battery chemistry and certification rows in the BOMs are marked safety-critical; no automation may substitute them.
- Prices customers pay. Systems compute costs and flag drift; the number on the store page is a human decision, on the record.
- The brand's word. Privacy promises, honesty copy, and this doctrine are written by the person accountable for them.