8ae0eb239a
Public demo of Factory 4 Life project management: - Gate definitions S0 (spec), S1 (build), S2 (integration), S3 (production ready) - Hardware project template with PlatformIO, KiCad CI, and Makefile for fab packages - JSON schema for .kill-life.yaml manifest - CLI scripts: create-project, validate-gates, dashboard with color-coded status output - Example project: led-controller (S0+S1 passed, S2 in progress)
1.3 KiB
1.3 KiB
Gate S1 — Build OK
Objectif
Valider que le projet compile, que les checks hardware passent, et que les tests unitaires sont en place.
Criteres par type
Firmware (si firmware/ existe)
pio runcompile sans erreur (au moins 1 environment)pio test -e nativepasse (ou justification documentee)- Pas de warnings critiques (-Werror ou equivalent)
Hardware (si hardware/ existe)
- ERC (Electrical Rules Check) green — artifact JSON
- DRC (Design Rules Check) green — artifact JSON
- Netlist exportable
- BOM genere (
hardware/bom/)
Software (si pas firmware/hardware)
- Build reussi (
npm run build/cargo build/ etc.) - Tests unitaires passent
- Linter/formatter OK
Criteres communs
- CI GitHub Actions configure et green
- README.md a jour avec instructions de build
- Gate S0 passee
Validation automatique
./scripts/validate-gates.sh <org>/<repo> --gate s1
Le workflow .github/workflows/kill-life-ci.yml execute automatiquement :
- ERC/DRC via
kicad-cli(containerghcr.io/inti-cmnb/kicad8_auto) - Build firmware via PlatformIO
- Validation BOM
Passage de gate
- CI green sur
main - PR avec label
gate:s1 - Mise a jour
.kill-life.yaml:s1.status: passed