mirror of
https://github.com/profullstack/logicsrc.git
synced 2026-09-10 19:26:00 +00:00
Anthony Ettinger
91834179b7
OpenPRD 0.2 fixed eight body sections, none of which asked what the thing is
built on or how it earns. The stack got chosen in the first implementation PR
instead of at review, and a PRD could be filled out completely without anyone
writing down who pays. PRD 0006 had already grown a hand-rolled
`## Business model` section, which is the gap showing.
0.3 adds two required sections between `UX Notes` and `Success Metrics`:
- Tech Stack — languages, frameworks, datastores, third-party services, and
anything the work must not depend on. It makes the requirements costable.
- Monetization — the revenue model: who pays, for what, how much, and when.
`_None._` stays a valid answer, but it now has to be said out loud.
Adding required sections would normally invalidate every document already
written, so a document is now held to the section list its own `openprd:` key
fixes. A 0.2 document keeps conforming with eight sections, forever; a 0.3
document needs ten. Adoption is per document, and `logicsrc prd validate
--expect-version 0.3` (new flag, wiring up the validator option that already
existed) reports the stragglers as OP-L-VERSION.
The front-matter schema is untouched — both additions are body sections.
Conformance bundle proves both directions: invalid/missing-monetization.md
fails with OP-C-SECTION-MISSING, and valid/legacy-0-2.md passes unedited.
This repo's own PRDs 0001-0006 stay at 0.2 as standing evidence that the
compatibility rule holds. PRD 0007 records the decision at 0.3.
Claude-Session: https://claude.ai/code/session_017XRNNm6pK6nPi7rJ6bJNHu
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
1.1 KiB
1.1 KiB
| openprd | id | title | status | authors | created | updated | repo | discussion | implementation | tags | supersedes | superseded-by | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 0.3 | 0000 | Short imperative title — start with a verb if possible | Draft |
|
2026-01-01 | 2026-01-01 |
Problem
The user/business problem, and why it matters now. Cite the ask, the incident, or the constraint — not aesthetics.
Goals
What success looks like, as outcomes (not features).
Non-Goals
Explicitly out of scope, to bound the work.
Users
Who this is for; personas or segments.
Requirements
- R1 [P0] First required capability.
- R2 [P1] Next capability.
UX Notes
Flows, states, and constraints that shape the experience.
Tech Stack
Languages, frameworks, datastores, and third-party services this will be built on, and anything it must not depend on.
Monetization
The revenue model: who pays, for what, how much, and when. None, when the change does not earn on its own.
Success Metrics
How the goals will be measured.
Risks & Open Questions
- Known risk or decision still owed.