L'électron rare
f55093d6fe
ESP-IDF CI / Host Tests (Unity) (push) Successful in 1m8s
CI / firmware-native (push) Successful in 2m57s
Rust Protection Tests / Cargo test (host) (push) Failing after 3m21s
ESP-IDF CI / ESP-IDF Build (v5.4) (push) Failing after 6m55s
ESP-IDF CI / Memory Budget Gate (push) Has been skipped
qa-cicd-environments / qa-kxkm-s3-build (push) Successful in 8m53s
qa-cicd-environments / qa-sim-host (push) Successful in 2m2s
qa-cicd-environments / qa-kxkm-s3-memory-budget (push) Successful in 11m17s
Context: the project archive (KXKM_Batterie_Parallelator-main) had no git history locally; a fresh repository is needed to host it on git.saillant.cc (electron/KXKM_Batterie_Parallelator). Approach: initialize a new repo on branch main, stage the archive content, and harden .gitignore before the first commit. Changes: - Import the full project tree: firmware/, firmware-idf/, firmware-rs/, iosApp/, kxkm-bmu-app/, kxkm-api/, hardware/, docs/, specs/, scripts/, models/, tests/ - Keep project dotfiles tracked despite the trailing '.*' ignore rule: .github/, .claude/, .superpowers/, .gitattributes, .markdownlint.json - Extend .gitignore: firmware/src/credentials.h (local secrets, template kept), kxkm-bmu-app/**/build/ (66 MB compiled iOS framework), .remember/ (session data) Impact: the project can now be maintained on the self-hosted Gitea forge with a clean, secret-free initial history.
24 lines
891 B
Markdown
24 lines
891 B
Markdown
# Gouvernance Integration BMU
|
|
|
|
## Objectif
|
|
Cadre d'execution unifie pour firmware, QA, ML et documentation afin de garantir surete, tracabilite et progression continue.
|
|
|
|
## RACI
|
|
| Domaine | Responsable | Approbateur | Support |
|
|
|---|---|---|---|
|
|
| Securite firmware | Firmware BMU Team | BMU Safety Review | SE: Security |
|
|
| QA/CI | QA Team | QA Gate | SE: DevOps/CI |
|
|
| ML pipeline | ML Team | SE: Architect | Explore |
|
|
| Plans/docs | Tech Writer | Tech Lead | Explore |
|
|
|
|
## Regles d'execution
|
|
1. Toute tache fermee doit fournir une evidence (commande, artefact, diff).
|
|
2. Tout blocage doit inclure cause + prochaine action concrete.
|
|
3. Les routes mutatrices web restent sous controle securite strict.
|
|
4. Les sorties ML restent consultatives, jamais autorite de securite.
|
|
|
|
## Escalade
|
|
- P0 surete: BMU Safety Review immediat.
|
|
- P1 QA/CI: QA Gate + DevOps/CI.
|
|
- P2 doc/process: Tech Writer.
|