Extend hardware-lifecycle pipeline with generative stages#194
Merged
Alan-Jowett merged 4 commits intomicrosoft:mainfrom Apr 7, 2026
Merged
Conversation
Update the hardware-lifecycle pipeline to interleave generative design stages with the existing adversarial audit stages. This is Step 9 of 9 — the final step in building the end-to-end hardware design workflow. The pipeline now flows: 1. author-requirements-doc -> requirements-document 2. design-schematic -> artifact-set (KiCad schematic + BOM) 3. review-schematic -> investigation-report (audit) 4. validate-simulation -> investigation-report (optional audit) 5. review-bom -> investigation-report (audit) 6. design-pcb-layout -> artifact-set (routed PCB + script) 7. review-layout -> investigation-report (audit) 8. emit-manufacturing-artifacts -> artifact-set (Gerbers, BOM, PnP) Previously the pipeline was audit-only (steps 1, 3, 4, 5, 7). The new stages (2, 6, 8) produce the design artifacts that the audit stages then review. The full workflow can also be run as a single interactive session using the hardware-design-workflow template (which orchestrates all stages with user gates and loop-back support). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the hardware-lifecycle pipeline definition in manifest.yaml to expand it from an audit-only flow into an end-to-end workflow that interleaves generative hardware design stages (schematic, PCB layout, manufacturing artifact emission) with the existing audit stages.
Changes:
- Updated
hardware-lifecyclepipeline description to reflect an interleaved design + audit workflow. - Inserted
design-schematic,design-pcb-layout, andemit-manufacturing-artifactsstages into the pipeline. - Added
artifact-setproduction/consumption contracts for the new design/manufacturing stages.
1. design-schematic had consumes: requirements-document but its template has input_contract: null (it does its own requirements discovery). Removed the consumes to match the template contract. Updated description to note design stages can optionally consume requirements or discover their own. 2. Audit stages (review-schematic, validate-simulation, review-bom, review-layout) only consumed requirements-document but also need the artifact-set produced by the preceding design stage. Updated to consumes: [requirements-document, artifact-set]. 3. emit-manufacturing-artifacts consumes artifact-set which is produced by design-pcb-layout, not by review-layout (which produces investigation-report). The ordering is correct (must audit before manufacturing) but the contract chain now correctly shows artifact-set flowing from design stages through audit stages to the next design stage. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1. Pipeline description was misleading about how stages chain. Reworded to accurately state that stages consume declared artifacts and may be used independently or sequentially. 2. Documented that audit stages provide an independent review pass even when the preceding design stage includes a self-audit. The redundancy is intentional: design-schematic self-audits for quick feedback, review-schematic provides a separate adversarial pass. 3. validate-simulation consumed artifact-set but simulation outputs (SPICE results, thermal analysis) are user-provided, not produced by design-schematic. Changed to consumes: requirements-document only, since the user provides simulation data separately. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Regenerated CATALOG.md via generate-catalog.js and updated the hardware-lifecycle pipeline diagram in README.md to include the new generative stages (design-schematic, design-pcb-layout, emit-manufacturing-artifacts) alongside the existing audit stages. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.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
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
Extend the
hardware-lifecyclepipeline to interleave generative design stages with the existing adversarial audit stages. This is Step 9 of 9 — the final step completing the end-to-end hardware design workflow.Changes
No new components — this PR only updates the
hardware-lifecyclepipeline definition inmanifest.yaml.Before (audit-only)
After (design + audit interleaved)
The new stages (design-schematic, design-pcb-layout, emit-manufacturing-artifacts) produce the design artifacts that the existing audit stages then review.
Design Decisions
Checklist
python tests/validate-manifest.py)