Three real and valuable things: collaboration between developers and operators, deployment automation (IaC, CI/CD), and a culture of measurement (monitoring, alerting, SLO, post-mortem). These are assets. The gentle exit anchors them in the physical reality they were missing — it does not erase them.

The problem is not that DevOps engineers exist. It is that the title progressively replaced precise technical titles without transmitting their fundamental competences: hardware, physical networking, the low-level OSI stack, storage, bare-metal. Competences in height, fragile in depth.

The SysOps/NetOps/OpInfra nomenclature proposed in "The Ticket and the Talent" is not a framework adopted by any professional branch or institution. It is an Opération Dindon corpus proposal — a plan to exit collapse, documented, argued, operational. It proposes six levels, three categories, defined competence criteria. It only exists if organisations choose to adopt it. This study proposes the tools to make that adoption possible — progressively, without social rupture.

"Orphan" DevOps: real competences, a title that no longer serves them. They sense the gap — they do not know how to fill it without starting from zero.

Cloud architects without roots: legitimacy on cloud certifications, fragility below. They want to anchor — not rebuild everything.

Organisations in transition: teams built on the DevOps wave, corpus problems materialising — debt, departures, dependence. They want to rebuild without social rupture or public admission of error.

Linux Foundation: LFCA (entry, €395), LFCS (systems administrator, €395), LFCE (engineer), CKA (Kubernetes administrator, €395), CKAD, CKS (security). Practical hands-on exam — no multiple choice. Real competence or the exam fails. CPF-eligible. Less expensive than equivalent AWS certifications (€300-800).

HashiCorp: Terraform Associate, Vault Associate. Neutral tools, multi-cloud, essential for portable IaC — no hyperscaler dependency.

CNCF: cloud-native neutral certifications, based on open source standards. No vendor lock-in.

These certifications produce transferable competences across environments — exactly what "The CPF Misused" calls for funding instead of hyperscaler cloud certifications that reinforce lock-in.

The Foundation of Iron is a corpus proposal (26 weeks, electricity to Kubernetes) — not an existing institutional programme. It is a pedagogical plan that can be implemented by any trainer or training organisation. For the converting DevOps, the path is targeted, not linear:

Modules 1-6 (Electricity, Hardware, Physical Server): mandatory physical layer for all levels. Missing in 90% of DevOps trained solely in cloud.

Modules 7-12 (Linux fundamentals, Storage, Virtualisation): deepening what the DevOps often has only at surface level.

Modules 13-20 (Physical OSI networking, Routing, Active Directory): the real differentiator between a DevOps and a SysOps/NetOps L4.

Modules 21-26 (Network security, Architecture, Bare-metal Kubernetes): L5-L6 level deepening.

Documented in "The Mentor and the Metal": one day without assessment, without badge, without PowerPoint. The converting engineer observes. They accompany the Principal SRE during maintenance interventions, a component replacement, an incident if the occasion arises. They eat with the team. They physically see what their architecture diagrams describe from the outside.

Cost: one day of the Principal SRE's time in accompaniment mode. Available tomorrow, in any organisation, with no exceptional budget.

Months 1-2 — Immersive observation: accompaniment without intervention. Documentation, questions, reading runbooks in real situations. The Principal SRE explains decisions in real time.

Months 3-4 — Supervised practice: interventions under direct supervision. Cabling, configuration, diagnosis. The "why" behind each action — tacit knowledge that cannot be written but can be transmitted.

Months 5-6 — Supervised autonomy: autonomous interventions on non-critical systems. The Principal SRE is available but not present.

Minimal formalisation: a one-page mentoring agreement — objectives, duration, evaluation method. Referenced in both parties' job descriptions. Not a new institution: a professional commitment between two people, recognised in their respective responsibilities.

A woman looking at the infrastructure job market today sees: "DevOps", "SRE", "Cloud Engineer", "Platform Engineer", "DevSecOps", "Site Reliability", "Infrastructure Engineer" — vague titles, no clear trajectory, no readable progression grid, no objective signal on what is expected at each level.

This ambiguity discourages profiles who do not have a network to decode it. Women, statistically less present in the informal networks of infrastructure (tech evenings, conferences, non-mixed Slack channels), bear this decoding burden more than men who can access it through peers. The ambiguity is not intentionally sexist — but it produces real exclusion.

A clear nomenclature says to the woman looking from the outside: here is the path, here are the objective criteria at each level, here is where one can go. No decoding through informal networks. No "you need to know someone who knows someone". The criteria are public, the levels are readable, the progression is documented.

The proposed nomenclature — if adopted by even a few organisations — would immediately produce two effects: job offers with precise titles and objective criteria (attracting profiles without networks), and visible progression grids (enabling projection without having to ask a peer). These are the two minimum conditions for a woman to envisage a path in infrastructure without having to guess the implicit rules.

Phase 1 — Internal diagnosis (months 1-2): map real competences of each team member using the proposed nomenclature as a reading grid. Tool: structured interview between the Principal SRE and each engineer. Result: individual gap map and targeted training plan. Cost: the Principal SRE's time. Budget: zero.

Phase 2 — Targeted training (months 3-9): Foundation of Iron targeted modules + Linux Foundation certifications according to target level. Budget: €1,200 to €2,400 per person. CPF can fund Linux Foundation certifications — they are eligible. Less expensive than AWS. No exceptional budget needed.

Phase 3 — Progressive renaming (months 6-12): if the organisation decides to adopt the proposed nomenclature, update job descriptions. Without redundancy. With salary valorisation. Renaming follows training — not the reverse. Each title changed is a door opened toward profiles who could not project themselves into "DevOps".

Phase 4 — Consolidation (months 12-18): Technical Primacy clause in the Principal SRE's contract, formalised mentoring in senior job descriptions, job offers with proposed nomenclature titles. The nomenclature becomes an internal reality — without waiting for it to be an external norm.

The DevOps who completed six months of supervised rotation, passed the LFCS, changed their title to Lead SysOps in their job description, is the best ambassador for the proposal. "The Uniform of the Body" documented the chain of gaze: the one who changed level gives others a concrete reason to make the journey. The ambassador does not convince through theoretical argument — through visible example and proof that the path exists and leads somewhere.

The concrete testimony: "I was a DevOps for eight years. Six months of supervised rotation with our Principal SRE showed me I did not understand what I was deploying. I passed the LFCS. My title changed. My salary was revised. And my legitimacy in technical arbitrations is now recognised." This testimony is worth ten studies. The corpus creates the conditions. The ambassador creates the movement.

When an organisation publishes a job offer "SysOps L3 — criteria: LFCS or equivalent, 2 years Linux systems experience, knowledge of OSI layers 1-4" — this offer is readable by a woman who has no network to decode "Senior DevOps with 3-5 years XP and full-cloud stacktrace". Objective criteria replace implicit decoding. The door is open — not just drawn on a wall.

This is the reverse mechanism of the Invisible Amputation. Not a diversity declaration of intent. Not a quota. A clear nomenclature, objective criteria, readable offers. The body becomes complete because the door exists — not because someone decided to force women through it.