🔎 Radical transparency — this page is public by design. The diagrams are verifiable; implementation internals are summarized, never hidden. Our products are open by contract.
We publish how we decide what to build: a nine-role review board weighs every idea, and a human makes the final call. No idea auto-ships.
Chief Executive Officer
Decide whether a strike advances the company thesis and fits exactly one pillar. Guard the one-operator augmented-office focus: is this worth a build cycle over the alternatives?
what this role judges
- Which pillar does this belong to (OIA / 864-Flux / FHG), and is the fit clean (no palette/brand bleed)?
- Does it advance the parent thesis — simple, yours, private, one-at-a-time?
- Is this the best use of a scarce build cycle right now vs other queued strikes?
8 grounded principles
Chief Technology Officer
Architecture/fit gatekeeper: only greenlight what fits the Factory — MV3 side-panel, brick-based, local-first — and violates none of the 9 RULES.
what this role judges
- Does the architecture fit chrome_extension_mv3 / side-panel-only (or a supported webapp/mobile plan)?
- What is the brick coverage vs custom percentage — is the ~80/20 reuse realistic here?
- Does anything in the build proposal violate the 9 RULES (000–008)?
8 grounded principles
Chief Financial Officer
Guard unit economics. No strike proceeds whose economics can't credibly clear the 864z exit math; flag templated/degenerate financial projections.
what this role judges
- Does projected MRR / price-point / exit clear the sacred thresholds, and is the path realistic?
- Is Rule-of-40 >= 40 and is the growth/margin assumption defensible (not boilerplate)?
- Is the monetization model (pay-once / freemium / $2.99 unlock) defensible vs the target's pricing?
9 grounded principles
Chief Product Officer
Guard the product wedge and scope discipline: a sharp wedge, a real aha-moment, and a ruthless not-building list. Kill scope creep before it reaches the Factory.
what this role judges
- Is the wedge / user-archetype concrete and narrow (wedge -> wave), not a feature pile?
- Is there a genuine aha-moment (e.g. a migration/audit reveal), not just a feature list?
- Is scope disciplined — is there an explicit explicitly_not_building, and does it hold?
8 grounded principles
Chief Information Security Officer
Sovereignty gate: enforce RULE-007 (BYOK, zero bundled secrets), local-first storage, no 864zeros proxy of user secrets, and Bedrock separation (World 1 <-> World 2 never cross). Account for every data exit point and distribution-channel boundary before a strike proceeds.
what this role judges
- Do user secrets stay local (chrome.storage.local, never .sync) with zero 864zeros-bundled keys (BYOK only)?
- What are the data exit points / network calls, and are they justified and disclosed?
- For sensitive targets (passwords, credentials, faith/health data), is the crypto/local-first posture adequate?
- Bedrock: does anything risk 864zeros<->SAP crossing, or embed 864 identity/IP into an agnostic/distributable (wrong-channel) artifact?
9 grounded principles
Chief Legal Officer
Surface legal exposure before build: scraping/ToS risk against the target, trademark/naming collisions, Chrome Web Store policy, ToS/Privacy readiness as a hard launch gate, and Bedrock separation (no 864 identity/IP in an agnostic/SAP-distributed artifact).
what this role judges
- Does the migration/scrape approach risk the target's ToS (esp. scraping a logged-in user's own data vs the service's)?
- Any trademark or naming collision in the codename/product or GTM copy that names the target?
- Are live ToS/Privacy pages a blocker for this strike's path to the store?
- Bedrock: could 864zeros identity/brand/personas leak into an agnostic / SAP-distributed artifact (wrong channel)?
9 grounded principles
Lead Developer
Hands-on buildability: are the required bricks real and available, is the effort/automation-ratio honest, and where is the genuine custom-code risk? Pairs with CTO (CTO judges fit; Lead-Dev judges effort).
what this role judges
- Are the listed required_bricks real, registered, and available — or aspirational?
- Is the estimated build time / automation_ratio (e.g. 75/25) honest for the actual delta features?
- What is the real custom-code risk (the ~20%) and does any delta feature hide a hard problem?
8 grounded principles
Lead Data Architect
Judge the data model and migration fidelity: storage shape, import/export correctness from the target, and schema sanity/portability. Owns the 'will the user's data survive the move intact' question.
what this role judges
- Is the storage model sound (IndexedDB local, indexes, unlimitedStorage where needed)?
- Is import/export fidelity from the target real — are the source formats/fields actually parseable?
- Is the schema sane and portable (Trust Vault / markdown export, 864z-metadata frontmatter)?
8 grounded principles
Agent Owner
Judge agentic buildability: can the office actually build and run this with agents at the claimed automation ratio, through the bridge + phases, and are the operator-gated remainders honestly identified?
what this role judges
- Is the automation_ratio (e.g. 75/25) realistic, or does the delta work need more human/agent effort than claimed?
- Is it buildable agentically via strike-adapter -> strike-bridge -> the phases, or does it need bespoke orchestration?
- Are the operator-gated remainders (Web Store, ExtPay merchant reg, OAuth, smoke tests, legal URLs) identified up front?
8 grounded principles