The Brief Pack
What we're building and why: the one-pass job, the availability gap, the architecture, the commercial model, and what's been done so far. Seven documents, ten minutes.
Tech Stack & Workflow Guide
New to the project? The stack, the conventions, and the voice-memo → brief → agent-session → debrief working method every dev replicates. Read before your first commit.
Reality: What Exists Today
The Librarian's ground truth — what exists vs what's PROPOSED, plus the decision log. If it's not in here, it doesn't exist.
The v0.1.20 Review Pack
The whole project reviewed nine days in — code, security, testing, CI, docs and this site — plus two proposals: the open engineering hub (the NFRs made public) and QA-to-docs (screenshot-verified user docs). Nine documents, honest throughout.
Audio-Transcribe Integration Pack
The implementation briefs: import the proven engine cross-origin, Web Components on the shared base, full JS-API compliance, ASCII mockups and data-flow diagrams.
Audio-Transcribe API & Capabilities
The code-verified embedding contract of the engine we build on: the window.__tool surface, events, typed errors, cost and spend-cap seams.
GitHub Pages + Route 53 Guide
How this site is hosted and how the domain works — the publish chain, the DNS mechanics, and the repeatable checklist for the next project.
First Product To Market (27 Jul)
The founding pack: the architecture brief (no backend, OpenRouter as inference + billing, privacy modes), the commercial strategy, and the partnership contract draft.
Home Page Redesign for Go-Live (8 Aug)
The brief for launching as VoiceDebrief for WhatsApp: put the workflow on the home page, delete the three privacy modes (two of which never existed) and say plainly that audio goes to OpenRouter and we cannot name or control the provider, add a beta mark and an LLM caveat, and explain how to get an OpenRouter key. It also asks the designer for a list of every claim on the current site that is not true.
Semantic Graphs over Transcripts (8 Aug)
A self-contained pack — both of the concept briefs verbatim, what the concept scheme actually built, the real data shapes, and an engineering review — asking for a worked simulation of concept graphs over a realistic voice-note corpus, before any of it is built. The visualisation cannot be designed from a schema, only from data.
The design candidates — runnable
The briefs below, actually running: three themes and four culture packs, each the same tool with a different answer. No key needed — they run a scripted sample at realistic speed. Opinions welcome; that is what they are for.
Three Designs for A/B Testing (8 Aug)
The design brief: three genuinely different bets on how this product should work, shipped alongside the current one so real users decide. Everything is on the table — and the conflict between A/B measurement and “nothing tracked” is named, not papered over.
Product Name Analysis (8 Aug)
Why the product should not be named “WhatsApp anything” (the mark belongs to Meta; the SERP head belongs to WhatsApp's own built-in transcripts), why the name should own the OUTPUT — the brief, not the transcription — and the proposal on the table. Decision: Dinis.
The Lineage Briefs
Where the thinking came from: open source as strategy, commercialising the primitives, and the nine-tools-ready-to-productise inventory.
The Infographics
Visual one-pagers of the briefs above — generated with the same infographic engine this product reuses.
The Team & Its Roles
The roster: Conductor, Architect, Dev, Designer, DevOps, Librarian, QA, AppSec, DPO, Ambassador, Journalist — how an agentic team plus humans builds this in the open.
The Work Queue
Issues-FS-lite: every task as a file, open/blocked/done, updated in the same commit as the work it describes.
The Changelog
What each version changed — captured by the Librarian and the Journalist together, one entry per tag.