forked from sethdford/shipwright
-
Notifications
You must be signed in to change notification settings - Fork 0
Pipeline Design 326
ezigus edited this page Apr 19, 2026
·
1 revision
I've completed the Architecture Decision Record (ADR) for issue #326, successfully delivering the design phase. Here's what's now available:
📄 File: docs/ADR_326_test_first_ruflo_enrichment.md
Complete ADR including:
- Problem Statement: Semantic context missing from TDD test generation
-
Decision: Enrich
stage_test_first()with recall before prompt + store after files written -
Chosen Approach:
- Recall at line 20 using
ruflo_recall_similar_outcomes(TASK_TYPE, ISSUE_LABELS) - Inject results into tdd_prompt heredoc as "## Similar Past Test Generations"
- Store at line 109 with key
test_first-PIPELINE_ID-timestamp
- Recall at line 20 using
- Alternatives Evaluated: 4 rejected approaches with detailed rationale
- Implementation Plan: Exact code locations, dependencies, data flow
- Validation Criteria: 8 checkpoints before merge
- Risk Analysis: 5 identified risks with mitigations
✅ Stored in namespace pipeline-31764-326 with semantic embeddings for future recall
📄 docs/PLAN_326_test_first_ruflo_enrichment.md — All assumptions pre-validated
The ADR is ready for build with these concrete steps:
| File | Modification |
|---|---|
scripts/lib/pipeline-stages-build.sh |
Add 3 code blocks (lines 20, 26, after 109) |
scripts/sw-ruflo-adapter-test.sh |
Add 4 test cases |
All insertion points verified, fail-open design documented, no breaking changes.
The pipeline can now proceed to the build stage to implement the design.