Goldfish

A voice recorder for meetings that listens, lets anyone in earshot turn its memory down by saying so, and forgets on a curve: who-said-what for days, the gist for up to 30 days, then only outcomes. It never speaks; it answers with light. No Wi-Fi.

Speculative product by Resolution Co, first described in the NPC Memo of 2025-12-24 ("Fixing Our Meeting Memory Problem"). This folder takes it from speculative design to a hardware development process.

Start here

  1. Contributing (people or agents): read AGENTS.md: the pipeline, the checks, the rules. The repo (github.com/rafaeldavid/goldfish) is private: ask the owner for access. The workbench's "Pick this up" section (Specification, section 12) and its Build files page, which has a source zip, carry the same steps.
  2. History and current state: BUILD-LOG.md, starting at "Start here"; open work is in BACKLOG.md, and the reasons are in 03-architecture/decisions/.
  3. The site: https://npc.here.now/demo-goldfish/ is the landing page; the workbench is at https://npc.here.now/demo-goldfish/workbench/, with the spec, the 3D model (with wires), the meeting and device simulators, parts, prints and build files.
  4. The kit: v01/ (CAD, BOM, wiring with a cut list, assembly, firmware, reader page).
  5. The protocol: protocol/, the Resolution Protocol, with Goldfish as one profile.
  6. Earlier material: 00-sources/ (the memo, verbatim), 01-concept/ (brief, ladder, market comparison), ROADMAP.md. 07-simulator/ is the first concept simulator, kept for history.

Layout

Folder Holds
00-sources/ Primary sources with provenance. Everything traces back here.
01-concept/ Brief, resolution ladder, open questions
02-requirements/ Requirements with IDs (P-, S-, N-), each tied to a source and a test
03-architecture/ System blocks, data lifecycle, architecture options; decisions/ holds ADRs
04-hardware/ Envelope, subsystems and candidate part families, power budget
05-firmware/ State machine running on the always-on MCU
06-protocol/ Room-agreement rules and the stream schema (the interoperable part)
07-simulator/ Interactive anatomy, stream and forgetting simulator (single HTML file, no build)
08-legal-ethics/ Consent, biometrics, threat model
09-validation/ Research studies, technical spikes, hardware verification
10-manufacturing/ Certification and production notes (later)
v01/ The v01 kit: CAD, viewer, BOM, wiring, assembly, firmware, reader

Conventions

# Goldfish

A voice recorder for meetings that listens, lets anyone in earshot turn its memory down by saying so, and forgets on a curve: who-said-what for days, the gist for up to 30 days, then only outcomes. It never speaks; it answers with light. No Wi-Fi.

Speculative product by Resolution Co, first described in the NPC Memo of 2025-12-24 ("Fixing Our Meeting Memory Problem"). This folder takes it from speculative design to a hardware development process.

## Start here

1. **Contributing (people or agents):** read [`AGENTS.md`](AGENTS.md): the pipeline, the checks, the rules. The repo (github.com/rafaeldavid/goldfish) is private: ask the owner for access. The workbench's "Pick this up" section (Specification, section 12) and its Build files page, which has a source zip, carry the same steps.
2. **History and current state:** [`BUILD-LOG.md`](BUILD-LOG.md), starting at "Start here"; open work is in [`BACKLOG.md`](BACKLOG.md), and the reasons are in `03-architecture/decisions/`.
3. **The site:** https://npc.here.now/demo-goldfish/ is the landing page; the workbench is at https://npc.here.now/demo-goldfish/workbench/, with the spec, the 3D model (with wires), the meeting and device simulators, parts, prints and build files.
4. **The kit:** [`v01/`](v01/README.md) (CAD, BOM, wiring with a cut list, assembly, firmware, reader page).
5. **The protocol:** [`protocol/`](protocol/README.md), the Resolution Protocol, with Goldfish as one profile.
6. **Earlier material:** `00-sources/` (the memo, verbatim), `01-concept/` (brief, ladder, market comparison), `ROADMAP.md`. `07-simulator/` is the first concept simulator, kept for history.

## Layout

| Folder | Holds |
|---|---|
| `00-sources/` | Primary sources with provenance. Everything traces back here. |
| `01-concept/` | Brief, resolution ladder, open questions |
| `02-requirements/` | Requirements with IDs (P-, S-, N-), each tied to a source and a test |
| `03-architecture/` | System blocks, data lifecycle, architecture options; `decisions/` holds ADRs |
| `04-hardware/` | Envelope, subsystems and candidate part families, power budget |
| `05-firmware/` | State machine running on the always-on MCU |
| `06-protocol/` | Room-agreement rules and the stream schema (the interoperable part) |
| `07-simulator/` | Interactive anatomy, stream and forgetting simulator (single HTML file, no build) |
| `08-legal-ethics/` | Consent, biometrics, threat model |
| `09-validation/` | Research studies, technical spikes, hardware verification |
| `10-manufacturing/` | Certification and production notes (later) |
| `v01/` | The v01 kit: CAD, viewer, BOM, wiring, assembly, firmware, reader |

## Conventions

- Quote sources; don't paraphrase them. Cite the file.
- Requirements and ADR numbers are stable — never renumber.
- Part numbers are candidates until a datasheet is checked and an ADR accepts them.
- Model-written text (summaries, distillations) is labelled as machine-generated, in the product and in these docs.