LOCAL-FIRST · PRIVACY-FIRST

864zeros — How We Build

A disciplined, checkpoint-gated build — the same six phases for every product.

6 phases Scaffold → UI → Feature → Polish → Proof → GTM & Launch

How we build — every product, every time (6)

Each phase is checkpoint-gated; never skip. Publish is the last step (Phase 6: the product page goes live before the extension is submitted).

Phase 1 10-15 minutes

Scaffold

A loadable Chrome extension with correct directory structure, valid manifest, and working service worker. No features. No UI beyond a placeholder. Just a skeleton that Chrome accepts.

Phase 2 20-30 minutes

UI Shell

A fully styled panel with all screens/views stubbed out, navigation working, empty states displayed, and OIA design system applied. No functional features yet — just the complete visual shell.

Phase 3 15-45 minutes per feature

Feature Build

Implement one feature at a time from the app brief's feature list. This phase is repeated for each feature, in priority order.

Phase 4 30-60 minutes

Polish

Production-quality finish. Animations, edge case handling, error boundaries, performance, and final QA before Chrome Web Store submission.

Phase 5 45-90 minutes

Proof

Every /lib/ module unit tested. Service worker message handling integration tested. Manual QA checklist passed. Regression baseline saved. Nothing ships without this phase.

Phase 6 60–120 minutes

GTM & Launch (Browser Extension Module)

Every Go-To-Market artifact authored, the product's landing page published live on 864zeros.com and verified, the Central DAM hydrated, and the submission package ready — before the extension is published to the Chrome Web Store. Publishing the extension is th…

864zeros LLC · radical transparency · verifiable proof, calibrated detail · 2026-09-09 · the diagrams are generated from the same registries our products are built from (code wins).