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>
115 lines
3.9 KiB
JSON
115 lines
3.9 KiB
JSON
{
|
|
"openprdConformance": "0.3",
|
|
"description": "Conformance fixtures for OpenPRD 0.3. Every valid fixture must parse and validate with no errors; every invalid fixture must fail with the stated code. `file` is the filename the fixture must be validated as, since the standard's rules depend on it. A document is held to the section list its own `openprd:` version fixes, so valid/legacy-0-2.md still conforms with the eight sections 0.2 defined.",
|
|
"valid": [
|
|
{
|
|
"fixture": "valid/minimal.md",
|
|
"file": "0001-expand-the-parked-domain-service.md"
|
|
},
|
|
{
|
|
"fixture": "valid/full.md",
|
|
"file": "0001-expand-the-parked-domain-service.md"
|
|
},
|
|
{
|
|
"fixture": "valid/bold-requirements.md",
|
|
"file": "0002-use-bold-requirement-markers.md"
|
|
},
|
|
{
|
|
"fixture": "valid/subsections.md",
|
|
"file": "0003-organize-a-long-requirements-section.md"
|
|
},
|
|
{
|
|
"fixture": "valid/superseded.md",
|
|
"file": "0004-retire-the-old-flow.md"
|
|
},
|
|
{
|
|
"fixture": "valid/none-sections.md",
|
|
"file": "0005-keep-every-section-even-when-empty.md"
|
|
},
|
|
{
|
|
"fixture": "valid/legacy-0-2.md",
|
|
"file": "0006-keep-a-0-2-document-valid.md",
|
|
"reason": "A 0.2 document has eight sections and must keep conforming under 0.3."
|
|
}
|
|
],
|
|
"invalid": [
|
|
{
|
|
"fixture": "invalid/missing-section.md",
|
|
"file": "0001-missing-a-section.md",
|
|
"code": "OP-C-SECTION-MISSING",
|
|
"reason": "The body sections are all required; Users is absent."
|
|
},
|
|
{
|
|
"fixture": "invalid/missing-monetization.md",
|
|
"file": "0001-omit-the-monetization-section.md",
|
|
"code": "OP-C-SECTION-MISSING",
|
|
"reason": "0.3 requires Tech Stack and Monetization; Monetization is absent."
|
|
},
|
|
{
|
|
"fixture": "invalid/out-of-order.md",
|
|
"file": "0001-sections-out-of-order.md",
|
|
"code": "OP-C-SECTION-ORDER",
|
|
"reason": "Sections must appear in the order the standard fixes."
|
|
},
|
|
{
|
|
"fixture": "invalid/id-mismatch.md",
|
|
"file": "0001-id-does-not-match.md",
|
|
"code": "OP-C-ID-MISMATCH",
|
|
"reason": "front-matter id must equal the filename's numeric prefix."
|
|
},
|
|
{
|
|
"fixture": "invalid/bad-status.md",
|
|
"file": "0001-unknown-status.md",
|
|
"code": "OP-C-FRONTMATTER",
|
|
"reason": "status must be one of the seven lifecycle values."
|
|
},
|
|
{
|
|
"fixture": "invalid/missing-title.md",
|
|
"file": "0001-no-title.md",
|
|
"code": "OP-C-FRONTMATTER",
|
|
"reason": "title is required."
|
|
},
|
|
{
|
|
"fixture": "invalid/bad-id-format.md",
|
|
"file": "0001-two-digit-id.md",
|
|
"code": "OP-C-FRONTMATTER",
|
|
"reason": "id must be four digits, zero-padded."
|
|
},
|
|
{
|
|
"fixture": "invalid/unknown-key.md",
|
|
"file": "0001-unknown-front-matter-key.md",
|
|
"code": "OP-C-FRONTMATTER",
|
|
"reason": "Unknown front-matter keys are rejected."
|
|
},
|
|
{
|
|
"fixture": "invalid/superseded-without-replacement.md",
|
|
"file": "0001-superseded-with-no-replacement.md",
|
|
"code": "OP-L-SUPERSEDED-BY",
|
|
"reason": "Superseded must name the PRD that replaces it."
|
|
},
|
|
{
|
|
"fixture": "invalid/duplicate-requirement.md",
|
|
"file": "0001-duplicate-requirement-id.md",
|
|
"code": "OP-L-REQ-DUPLICATE",
|
|
"reason": "Requirement ids must be unique within a PRD."
|
|
},
|
|
{
|
|
"fixture": "invalid/dates-backwards.md",
|
|
"file": "0001-updated-before-created.md",
|
|
"code": "OP-L-DATE-ORDER",
|
|
"reason": "updated cannot precede created."
|
|
},
|
|
{
|
|
"fixture": "invalid/no-front-matter.md",
|
|
"file": "0001-no-front-matter.md",
|
|
"code": "OP-P-PARSE",
|
|
"reason": "A PRD must open with a YAML front-matter block."
|
|
},
|
|
{
|
|
"fixture": "invalid/bad-filename.md",
|
|
"file": "notes.md",
|
|
"code": "OP-C-FILENAME",
|
|
"reason": "A PRD lives at prd/<id>-<slug>.md with a four-digit id."
|
|
}
|
|
]
|
|
}
|