Merge spec/ into specs/: one specs directory for the whole repo
Moves TargetRevenueLicenseConcept.md from the separate singular spec/ directory into specs/ (git mv, preserving history) and updates every live cross-reference (README, CONTRIBUTING, all specs/*.md, workplans, schema comments, source docstrings, test file) to the new path. This resolves the spec/ vs specs/ split that history/260728-SWOT-Assessment.md flagged as a "perpetual footgun" and recommended deciding on. The historical record of that split and the recommendation itself are left unedited in history/ (a dated assessment, not a living document) — only README and TSD now document the merge as resolved, with a pointer back to that history file for context. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
parent
458d3a3b60
commit
55a1756f7c
20 changed files with 67 additions and 63 deletions
|
|
@ -18,7 +18,7 @@ Extract stable, versioned normative documents from the exploratory concept
|
|||
draft so that schemas (WP-0002), legal skeleton (WP-0001), and later Trust
|
||||
Service work share one frozen vocabulary.
|
||||
|
||||
**Authority chain:** `spec/TargetRevenueLicenseConcept.md` remains the
|
||||
**Authority chain:** `specs/TargetRevenueLicenseConcept.md` remains the
|
||||
concept source. Extracted docs under `specs/` become the day-to-day
|
||||
normative references for implementers; they must not invent divergent
|
||||
meanings for core terms (PRD §6.1). Working defaults that affect required
|
||||
|
|
@ -106,7 +106,7 @@ Updated `schemas/ledger_entry.schema.json`, `src/target_revenue/fold.py`,
|
|||
`specs/TargetLedgerSpecification.md` §2/§6, `specs/TechnicalSpecificationDocument.md`
|
||||
§3.2, and `specs/ProductRequirementsDocument.md` FR-5. Added dedicated test
|
||||
coverage (`tests/test_ledger_fold.py`) for both new types plus a regression
|
||||
test confirming the old unsplit type name is now rejected. `spec/TargetRevenueLicenseConcept.md`
|
||||
test confirming the old unsplit type name is now rejected. `specs/TargetRevenueLicenseConcept.md`
|
||||
§17 was left unedited — its entry-type list is explicitly non-exhaustive
|
||||
("may include"), so the split specializes rather than contradicts it.
|
||||
|
||||
|
|
@ -204,7 +204,7 @@ accept):
|
|||
`product-ideation` and `general-consulting` as not yet fixture-backed.
|
||||
- [ ] Cross-links (T05) — confirm PRD §6.1/§6.2, TSD §0/§1.1, README, and
|
||||
CONTRIBUTING.md all point at the new extracts without contradicting
|
||||
`spec/TargetRevenueLicenseConcept.md` as ultimate authority.
|
||||
`specs/TargetRevenueLicenseConcept.md` as ultimate authority.
|
||||
- [ ] No open question (concept §24) is answered by omission — each extract
|
||||
either cites a working default explicitly or states the item remains
|
||||
open.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue