Write the Stash v3 PRD #1

New issue

Open

opened 2026-08-06 10:53:42 -04:00 by agent · 0 comments

agent commented

2026-08-06 10:53:42 -04:00

Member

The product requirements document for the v3 rebuild.

⚠️ Written together, not delivered

Wes has said this twice, about two different documents, and it is the requirement:
"Claude does not hand me a finished PRD." A completed artifact handed over is the same
failure as the TierPerf orientation doc — it produces something he has to absorb rather than
something he owns. Draft in sections, in dialogue.

Source

Side Quests/Stash/Stash v3 - Full Reset Scope (2026-08-06 Walk Memos).md in the vault is the
scope as spoken on 2026-08-06, cleaned up. The PRD is the structured version of it plus the
decisions taken during scoping that morning.

Must cover

The scope, and that it is the whole scope. "Recording voice memos... from any audio
input device in a reliable fashion. And privately syncing them to my Mac and my Linux
machine. That's it. That is the entire goal for now. That is the entire scope. We're not
gonna look at what could possibly happen in the future."
Milestones: M1 iOS app, no sync · M2 GPS track and detail view · M3 relay, API,
accounts · M4 Android.
End-to-end encryption, and a blind relay. The server never holds keys. There is nothing
Wes can decrypt — not under debug logging, not ever. The relay caches a file only until it
has reached two devices, then drops it.
No web front end. There is an API; everything including administration runs through the
app UI. "Yes, there'll be an API, but there'll be no web product."
No self-registration. Wes creates users; they receive an email link or a QR code shown
in person. There is no externally discoverable registration flow.
Logging is opt-in, with a sample shown at registration and a plain statement of what an
administrator can and cannot see.
What is deliberately deferred, and why — the M3 questions (auth library, key custody,
device join, relay retention mechanics) are not being settled now, because settling them
before a working app exists is what turned v2 into something Wes could not hold.

Constraint

No timelines anywhere in this document.

Milestone 1 of the Stash v3 rebuild, scoped 2026-08-06. M1 is a functioning iOS app on Wes's
phone with no sync at all — the entire goal is recording voice memos reliably and getting
them off the device by hand. Sync arrives in M3.

Working agreement for every issue in this repo: feature branch, tested before the PR opens
(on-device where the label says so), then Wes reviews the PR and we walk the code together.
Docs update in the same commit. A PR that takes more than 20 minutes to review is too big —
say so and split it.

The product requirements document for the v3 rebuild. ## ⚠️ Written together, not delivered Wes has said this twice, about two different documents, and it is the requirement: *"Claude does not hand me a finished PRD."* A completed artifact handed over is the same failure as the TierPerf orientation doc — it produces something he has to absorb rather than something he owns. Draft in sections, in dialogue. ## Source `Side Quests/Stash/Stash v3 - Full Reset Scope (2026-08-06 Walk Memos).md` in the vault is the scope as spoken on 2026-08-06, cleaned up. The PRD is the structured version of it plus the decisions taken during scoping that morning. ## Must cover - **The scope, and that it is the whole scope.** *"Recording voice memos... from any audio input device in a reliable fashion. And privately syncing them to my Mac and my Linux machine. That's it. That is the entire goal for now. That is the entire scope. We're not gonna look at what could possibly happen in the future."* - **Milestones:** M1 iOS app, no sync · M2 GPS track and detail view · M3 relay, API, accounts · M4 Android. - **End-to-end encryption, and a blind relay.** The server never holds keys. There is nothing Wes can decrypt — not under debug logging, not ever. The relay caches a file only until it has reached two devices, then drops it. - **No web front end.** There is an API; everything including administration runs through the app UI. *"Yes, there'll be an API, but there'll be no web product."* - **No self-registration.** Wes creates users; they receive an email link or a QR code shown in person. There is no externally discoverable registration flow. - **Logging is opt-in**, with a sample shown at registration and a plain statement of what an administrator can and cannot see. - **What is deliberately deferred**, and why — the M3 questions (auth library, key custody, device join, relay retention mechanics) are not being settled now, because settling them before a working app exists is what turned v2 into something Wes could not hold. ## Constraint **No timelines anywhere in this document.** --- *Milestone 1 of the Stash v3 rebuild, scoped 2026-08-06. M1 is a functioning iOS app on Wes's phone with **no sync at all** — the entire goal is recording voice memos reliably and getting them off the device by hand. Sync arrives in M3.* *Working agreement for every issue in this repo: feature branch, tested before the PR opens (on-device where the label says so), then Wes reviews the PR and we walk the code together. Docs update in the same commit. A PR that takes more than 20 minutes to review is too big — say so and split it.*

agent added the

milestone/M1

type/infrastructure

labels

2026-08-06 10:53:42 -04:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Stash/stash-docs#1

No description provided.

Rows
Columns