WIP: migrate specs to SDP and prune mechanical scenario mirrors - #1
Draft
darko-mijic wants to merge 6 commits into
Draft
WIP: migrate specs to SDP and prune mechanical scenario mirrors#1darko-mijic wants to merge 6 commits into
darko-mijic wants to merge 6 commits into
Conversation
Replace @libar-dev/architect with a local @libar-dev/software-delivery-protocol link, author Specs/Packs under specs/, bind former architect patterns via codeAnchor, strip live @architect delivery tags, and guard the cutover with vitest plus sdp build/validate.
Author one idea-rung Spec per packages/examples/apps .feature file under specs/behavior/, pack them by family, and require the corpus to hold at least 200 Specs so the hundreds-scale delivery corpus is in the graph.
Add one example Spec per Gherkin Scenario (~3463) beside the parent behavior Specs, and author unimplemented backlog Specs from architect pending deliverables plus docs-living remaining/current work.
Rewrite example Specs with Given/When/Then from the Cucumber scenarios (including Background), and enrich architect/unimplemented Specs with problem, rules, decision, and remaining-work prose instead of titles only.
Move the former top-level architect/ specs, decisions, and releases out of the live tree so specs/ is the delivery corpus. Leave architect/README.md as a pointer. Cucumber tests stay in packages/examples/apps.
…amples
Delete 3,378 low-value SDP carriers: title-echo example mirrors of unit-level
Gherkin scenarios (platform-* and order-management deciders), all
architect-scenario stubs, and docs-living status dumps under
specs/unimplemented/{current,remaining}. Feature files remain the executable
carriers; example Specs are kept only for user-facing frontend flows and
cross-component order-management business flows (103 examples). Revert
readiness to idea on parents whose only evidence was pruned, relax the
migration-guard thresholds, and finish the protocol upgrade pass (verifies
relations, authored outcomes) across the surviving corpus.
Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/lineage/.platform-*, order-management deciders), allarchitect-scenariosstubs, andspecs/unimplemented/{current,remaining}status dumps..featurefiles remain the executable carriers.readinesstoideaon parents whose only evidence was pruned; relaxsdp-migration-guardthresholds accordingly.Verification
pnpm sdp:build: 640 specs, 14 packs, 0 errorspnpm sdp:validate: 0 errors, 103 warnings (pre-existing verifies-linkage class)pnpm vitest run test/sdp-migration-guard.test.ts: 4/4 passingMade with Cursor