What runs, what is tested, what isn't — without rounding.

E2E sandbox certification

Verdict: ABSENT — across every repository audited here.

None of the repositories audited here has an end-to-end certification harness. Almost all CI measures doctrine (garde-fous.yml script: no frontier provider at runtime, no secret tracked by git, no Elzéard credential) — not the product. A green garde-fous badge says nothing about whether the code compiles, runs, or serves real traffic — and a red badge today doesn't say more either (see "CI status" below, reviewed in depth on 2026-09-08: the 08/26 billing cause is resolved, but per-repository reactivation isn't).

What an e2e certification would actually require

"ABSENT" isn't a checkbox — it's the absence of a mechanism that would combine four properties at once:

The closest thing to an e2e certification (aiame-fin, aiame-red) remains fragmented across these four properties — see this page's history for the detail, mechanism by mechanism. What has changed since the last audit (2026-08-13/17): CI itself is no longer a reliable signal today, org-wide — see below.

CI status — billing is resolved, reactivation isn't

Regression found on 2026-09-24: the only complete reactivation this page has ever documented has since been re-disabled. The billing block observed on 2026-08-26 remains resolved at the org level (gh api orgs/aiame-fr/actions/permissions still confirms enabled_repositories: all today) — but aiame-miroir, reactivated and green on 2026-09-02 (PR#16, 4 jobs on real runners), shows enabled: false live today, despite a real, green run as recent as 2026-09-22 (run 35692425622). Someone or something switched off Actions for this repository between the 22nd and the 24th — not a new billing outage (the org remains open), a repo-local regression, cause unidentified. There is therefore no longer any verified example of a complete reactivation that held over time in this org.

The rest of the fleet never caught up either. Re-verified repository by repository on 2026-09-24 (gh api repos/aiame-fr/<repo>/actions/permissions, org grown from 36 to 40 repositories since the last pass): 37 of the 38 non-archived, non-fork repositories in the org have Actions disabled at the repository level (36 confirmed on 09-08, the proportion hasn't moved) — a switch left OFF since 08/27 for most, not a new outage. The only verified exception today is aiame-knowledge, whose scheduled workflow (knowledge-refresh.yml) justifies Actions deliberately staying active there. No run (not even workflow_dispatch) has been able to execute on the disabled repositories since 08/26 or 27, regardless of how many commits/PRs have merged since. Enforcement shifted, repository by repository, to a local git hook (.githooks/pre-push) introduced the same week — but that hook is not versioned as active: every clone/worktree must run git config core.hooksPath .githooks itself, without which no check exists at all (the hook's own comment on aiame-store says it in black and white: "NOT ACTIVE on a fresh clone/worktree").

Edge case found on 09-08, not re-verified since: aiame-ledger did retry two runs on 06-09 (workflow_dispatch, not the silence the previous version of this page claimed) — but both remain stuck in queued, never assigned to a runner, more than 2 days later. A distinct problem from the org-wide billing issue (see "CI status"), never resolved or even retried.

Each relevant card below reports its own live-verified state — some date from 09-08, others from 09-24 (see each card). aiame-graine was never affected (Actions triggers on push/PR, checks green on HEAD). This section is dated today; like the rest of the page, it goes stale.

Method

Three classes, defined by evidence, never by the ambition declared in a repository's own README:

Fully redone on 2026-08-26: the 30 repositories declared in repos.json were re-read one by one — CI (gh api, job logs, not just the badge), real code, a live HTTP request on every plausible URL. 11 repositories had never appeared on this page before (see "Inventory gaps" below); 7 changed tier since the last audit (2026-08-13/17) in light of new evidence, not a new scoring policy.

Prod — 11 repositories

Pre-prod — 17 repositories

Dev — 9 repositories

Inventory gaps — resolved 2026-08-26, reopened 2026-09-08, reopened again 2026-09-24

11 of 30 repositories existed in repos.json without ever having appeared on this page: aiame-agri-gers, aiame-auth, aiame-dream, aiame-ivx, aiame-ledger, aiame-mcp, aiame-optaplanner, aiame-price, aiame-scheduler, aiame-sov-kernel, aiame-store. Two of them (aiame-auth, aiame-optaplanner/Angel) are public services that had already been in production for several days — the omission wasn't neutral, it left two entire prod repositories outside the audit. The 19 other classifications from the previous audit (2026-08-13/17) were fully re-read rather than carried over as-is; 7 changed tier in light of new evidence (detail in each card above), not 5 as this page once claimed — two changes (aiame-one, aiame-prd) had been applied to the cards without being counted in that sentence, found by re-reading this page afterward, corrected here rather than left as is: aiame-sov and services-manager (dev → prod), aiame-fin (pre-prod → prod), aiame-core, aiame-rag and aiame-one (dev → pre-prod), aiame-prd (pre-prod → dev). aiame-miroir, which only had a provisional "post-audit" section while awaiting proof of deployment, is now a normal pre-prod card.

Reopened on 2026-09-08: the same class of gap reproduced 13 days later. The org has 36 repositories, not 30 — 3 truly deserved a card (aiame-angel, aiame-compliance, aiame-graine, all audited above), bringing the total to 33. Two other names found (aiame-tf, changedetection.io) turned out to be false leads already settled elsewhere — aiame-tf is archived, its content merged into aiame-infra/terraform/dns/; changedetection.io is a public fork of a third-party tool, never deployed by AIAME — both are correctly declared in excluded[] of repos.json on main, only the working copy used for this review was temporarily missing it. repos.json itself therefore needs no correction.

Reopened on 2026-09-24: the same class of gap, a third time in a month. The org has 40 repositories, not 36 — 4 new repositories created since the last pass (aiame-racines, aiame-rag-core, aiame-voice, aiame-guard, all created between 09/10 and 09/18) truly deserved a card, all audited above, bringing the total to 37.

A fifth name found, aiame-workspace (created 08/07 — not new, simply never audited), turned out to be a false lead of the same kind as aiame-tf/changedetection.io: its own README says so explicitly, versioned root tooling, no product code. Excluded from this page for that reason, not a separate omission. aiame-tf and changedetection.io themselves remain correctly excluded, nothing to fix there.

Side effect found during this review, unrelated to the inventory itself: aiame-miroir's CI reactivation documented on 09-08 has since regressed — see "CI status" and its card.

This is exactly the kind of drift ./bootstrap.sh --check exists to catch — this portfolio doesn't replace that verification, it gives a snapshot dated 2026-09-24. Third reopening in a month (08-26, 09-08, 09-24): this portfolio is itself exactly the example it denounces at the top of the page — a snapshot that goes stale, never a continuous mechanism.