Lab651 Process
Everything we’ve learned about building, selling, and running Lab651 — searchable, version-controlled, AI-queryable. Think of this as the upkeep-worthy replacement for the old Google Sites intranet; let’s get 80% and iterate.
Sections
- Engineering — the canonical fullstack cheatsheet.
- Engineering Management — client interactions, quoting, retros, stand-ups, EOS with engineers.
- How we Work — Harvest, Google Drive, and the EOS operating system.
- Marketing — brand, collateral, outbound tooling, marketing-ops.
- Operations — facility, HR, finance, annual-calendar rhythms.
- Project Management — kickoff, estimation, discovery, retrospectives, delivery.
- Sales Cycle — inquiry → signed SOW → client survey → testimonial.
- Security Policies — data, access, incident reporting, continuity, DR (legal/compliance pass pending).
- Software Best Practices — historical SDLC, charter templates, branching-model references.
The shape above mirrors the old intranet intentionally. First pass is
fidelity; the grooming pass cleans up voice, wiki-links the cross-references,
and restructures as needed. See
plans/2026-04-19-intranet-migration.md
for what still needs doing.
How this site works
- Source of truth is markdown in git. Every page here lives under
docs/in the repo. AI tools can read it, humans can PR it, history is preserved forever. - All changes go through PRs. That’s the audit trail. If something’s stale, open a PR to update or archive it.
- Quarterly review ritual. Every doc has an
ownerand alastRevieweddate. We sweep through each quarter and clear out rot. - Authenticated. You’re here because you’re signed in with a Lab651 account via Cloudflare Access.
Migration status
Two internal Google Sites (89 + 54 pages) have been migrated into the
sections above — 112 live pages across 10 sections. Of the 143 source pages,
104 were kept, 10 had useful nuggets salvaged into other pages, and the rest
were skipped as redundant or outdated. Original source files are preserved in
archive/
for reference.