Construit en public.
Chaque changement important de Wombat commence par une Request for Comments ou un Architecture Decision Record public. Cette page suit chaque décision, du premier brouillon au merge, pour que rien ne reste caché.
Toutes les Requests for Comments.
Filtrez par projet et par statut, lisez les résumés et suivez les discussions et pull requests associées.
Framework
RFC-0001
Initial 7-pillar framework structure
Establishes the core seven-pillar model as the foundational structure of Wombat. Extended to eight pillars by RFC-0012.
RFC-0002
Public 2026 roadmap and milestone planning
Defines the public roadmap for 2026 covering Q1–Q4 milestones, v1.0 target, pilot programme, and foundation readiness goals.
RFC-0003
Pillar descriptions and key questions — 7 pillars
Adds the initial content definition for each of the 7 pillars. Later extended to cover the 8th Agentic pillar (RFC-0012).
RFC-0004
Documentation migration to AsciiDoc / Antora
Migrates all framework documentation from Markdown to AsciiDoc and establishes Antora as the documentation build system with component versioning.
RFC-0005
Contribution metadata — CONTRIBUTING, CODE_OF_CONDUCT, SECURITY
Adds the standard open-source health files to the framework repository.
RFC-0006
Sovereign pillar (Pillar 7) — initial controls
Introduces the Sovereign pillar as the 7th pillar of Wombat with 10 initial controls (WAF-SOV-010 through WAF-SOV-100).
RFC-0007
Governance refactor — modular best practices, case studies and navigation
Restructures the Governance pillar into modular best-practice pages and adds case-study content.
RFC-0008
Controls schema v1 — machine-readable YAML specification
Defines a formal schema for Wombat controls YAML files, enabling validation and tooling integration for the 83+ controls library.
RFC-0009
PASS scoring model — formal specification for v1.0
Formalises the PASS scoring model as a normative specification for tier definitions, calculation rules, aggregation logic, and versioning contract.
RFC-0010
Assessment tooling — CLI and scorecard approach
Defines the approach for official Wombat assessment tooling including the WOMBATpass CLI, server, dashboard, and web scorecard.
RFC-0011
CI/CD pipeline for framework and tooling repositories
Introduces automated checks and release workflows for framework, wafpass-core, wafpass-server, and wafpass-dashboard repositories.
RFC-0012
Agentic pillar as the 8th pillar
Adds the Agentic pillar as the 8th pillar of Wombat with 10 initial controls, regulatory mappings, and bilingual documentation.
RFC-0016
Control-level remediation playbooks
Standardises machine- and human-readable remediation guidance for every Wombat control so operators can act on findings directly.
RFC-0017
Multi-cloud provider expansion beyond AWS and SINA Cloud
Defines how WOMBATpass detection and controls will be extended to cover Azure, GCP, and other cloud providers while keeping the framework cloud-agnostic.
RFC-GH-framework-26
RFC: Quality Assurance
CI checks for dead xrefs, unregistered nav.adoc files, and control-schema consistency between YAML, AsciiDoc, and navigation.
RFC-GH-framework-25
RFC: Expand Sovereign & Resources
Expand Sovereign definitions, evidence matrix, and create real overview/glossary pages for resources and wording.
RFC-GH-framework-23
RFC: Complete the Agentic Pillar
Complete Agentic pillar maturity, evidence, glossary, and best-practice pages with examples.
RFC-GH-framework-22
RFC: Consolidate Navigation & Links
Standardise module links, convert relative xrefs to module-prefixed xrefs, and clean Markdown links.
RFC-GH-framework-21
RFC: Finalize Antora Structure
Finalise antora.yml registration, create pillar-security nav, update README/AGENTS for 8-module layout.
RFC-GH-framework-24
RFC: Correct and Expand the Controls Catalog
Align controls to 8 pillars, add Agentic, and extend control-schema.adoc.
Framework · Ouvertes à la relecture
RFC-GH-framework-26
RFC: Quality Assurance
CI checks for dead xrefs, unregistered nav.adoc files, and control-schema consistency between YAML, AsciiDoc, and navigation.
RFC-GH-framework-25
RFC: Expand Sovereign & Resources
Expand Sovereign definitions, evidence matrix, and create real overview/glossary pages for resources and wording.
RFC-GH-framework-23
RFC: Complete the Agentic Pillar
Complete Agentic pillar maturity, evidence, glossary, and best-practice pages with examples.
RFC-GH-framework-22
RFC: Consolidate Navigation & Links
Standardise module links, convert relative xrefs to module-prefixed xrefs, and clean Markdown links.
RFC-GH-framework-21
RFC: Finalize Antora Structure
Finalise antora.yml registration, create pillar-security nav, update README/AGENTS for 8-module layout.
RFC-GH-framework-24
RFC: Correct and Expand the Controls Catalog
Align controls to 8 pillars, add Agentic, and extend control-schema.adoc.
Framework · Brouillons
RFC-0016
Control-level remediation playbooks
Standardises machine- and human-readable remediation guidance for every Wombat control so operators can act on findings directly.
RFC-0017
Multi-cloud provider expansion beyond AWS and SINA Cloud
Defines how WOMBATpass detection and controls will be extended to cover Azure, GCP, and other cloud providers while keeping the framework cloud-agnostic.
Framework · Décidées / mises en œuvre
RFC-0001
Initial 7-pillar framework structure
Establishes the core seven-pillar model as the foundational structure of Wombat. Extended to eight pillars by RFC-0012.
RFC-0002
Public 2026 roadmap and milestone planning
Defines the public roadmap for 2026 covering Q1–Q4 milestones, v1.0 target, pilot programme, and foundation readiness goals.
RFC-0003
Pillar descriptions and key questions — 7 pillars
Adds the initial content definition for each of the 7 pillars. Later extended to cover the 8th Agentic pillar (RFC-0012).
RFC-0004
Documentation migration to AsciiDoc / Antora
Migrates all framework documentation from Markdown to AsciiDoc and establishes Antora as the documentation build system with component versioning.
RFC-0005
Contribution metadata — CONTRIBUTING, CODE_OF_CONDUCT, SECURITY
Adds the standard open-source health files to the framework repository.
RFC-0006
Sovereign pillar (Pillar 7) — initial controls
Introduces the Sovereign pillar as the 7th pillar of Wombat with 10 initial controls (WAF-SOV-010 through WAF-SOV-100).
RFC-0007
Governance refactor — modular best practices, case studies and navigation
Restructures the Governance pillar into modular best-practice pages and adds case-study content.
RFC-0008
Controls schema v1 — machine-readable YAML specification
Defines a formal schema for Wombat controls YAML files, enabling validation and tooling integration for the 83+ controls library.
RFC-0009
PASS scoring model — formal specification for v1.0
Formalises the PASS scoring model as a normative specification for tier definitions, calculation rules, aggregation logic, and versioning contract.
RFC-0010
Assessment tooling — CLI and scorecard approach
Defines the approach for official Wombat assessment tooling including the WOMBATpass CLI, server, dashboard, and web scorecard.
RFC-0011
CI/CD pipeline for framework and tooling repositories
Introduces automated checks and release workflows for framework, wafpass-core, wafpass-server, and wafpass-dashboard repositories.
RFC-0012
Agentic pillar as the 8th pillar
Adds the Agentic pillar as the 8th pillar of Wombat with 10 initial controls, regulatory mappings, and bilingual documentation.
Core
RFC-0013
WOMBATpass support for Pillar-8 Agentic
Extends WOMBATpass CLI, server, and dashboard to evaluate the Agentic pillar controls as part of a full PASS assessment.
RFC-0014
WOMBATpass CLI / Server / Dashboard v1.1.0 release
Releases WOMBATpass CLI v1.1.0, Server v1.1.0, and Dashboard v1.1.0 with Pillar-8 Agentic support, detection fixes, and SINA Cloud region detection.
RFC-GH-wafpass-core-41
Feature Request: Comprehensive Test/Quality Coverage Implementation Plan
Unify fragmented test and coverage strategy across wafpass-core, server, and dashboard.
RFC-GH-wafpass-core-42
Feature Request: API Versioning and Backwards-Compatibility Strategy for WOMBATpass
Define API maturity, backwards-compatibility rules, and versioning strategy for WOMBATpass APIs.
RFC-GH-wafpass-core-43
Feature Request: Source Snapshots — Ingestion Contract and Reliable Upload Path
Define a reliable source-snapshot ingestion contract so dashboard preview and auto-fix work consistently.
RFC-GH-wafpass-core-40
Feature Request: Dashboard UX Overhaul — Guided Onboarding, Role-Based Landing, and Progressive Disclosure
Reduce dashboard navigation fragmentation and add guided onboarding with role-based landing pages.
RFC-GH-wafpass-core-39
Feature Request: Implement Action-Oriented Notifications
Make dashboard notifications actionable instead of passive text displays.
RFC-GH-wafpass-core-38
Feature Request: Implement Control Packs Marketplace
Expand the control-packs feature beyond admin-only uploads to a real marketplace with discovery and governance.
RFC-GH-wafpass-core-37
Feature Request: Implement Maturity-Tier Enforcement Policy Gates
Tie maturity tiers to CI/CD policy gates so pipelines can block promotion below a target tier.
Core · Ouvertes à la relecture
RFC-GH-wafpass-core-41
Feature Request: Comprehensive Test/Quality Coverage Implementation Plan
Unify fragmented test and coverage strategy across wafpass-core, server, and dashboard.
RFC-GH-wafpass-core-42
Feature Request: API Versioning and Backwards-Compatibility Strategy for WOMBATpass
Define API maturity, backwards-compatibility rules, and versioning strategy for WOMBATpass APIs.
RFC-GH-wafpass-core-43
Feature Request: Source Snapshots — Ingestion Contract and Reliable Upload Path
Define a reliable source-snapshot ingestion contract so dashboard preview and auto-fix work consistently.
RFC-GH-wafpass-core-40
Feature Request: Dashboard UX Overhaul — Guided Onboarding, Role-Based Landing, and Progressive Disclosure
Reduce dashboard navigation fragmentation and add guided onboarding with role-based landing pages.
RFC-GH-wafpass-core-39
Feature Request: Implement Action-Oriented Notifications
Make dashboard notifications actionable instead of passive text displays.
RFC-GH-wafpass-core-38
Feature Request: Implement Control Packs Marketplace
Expand the control-packs feature beyond admin-only uploads to a real marketplace with discovery and governance.
RFC-GH-wafpass-core-37
Feature Request: Implement Maturity-Tier Enforcement Policy Gates
Tie maturity tiers to CI/CD policy gates so pipelines can block promotion below a target tier.
Core · Décidées / mises en œuvre
RFC-0013
WOMBATpass support for Pillar-8 Agentic
Extends WOMBATpass CLI, server, and dashboard to evaluate the Agentic pillar controls as part of a full PASS assessment.
RFC-0014
WOMBATpass CLI / Server / Dashboard v1.1.0 release
Releases WOMBATpass CLI v1.1.0, Server v1.1.0, and Dashboard v1.1.0 with Pillar-8 Agentic support, detection fixes, and SINA Cloud region detection.
MCP
RFC-GH-wafpass-mcp-7
RFC-5: Role-aware natural tool aliasing
Allow curated aliases for long auto-generated MCP tool names so LLMs can match them more naturally.
RFC-GH-wafpass-mcp-4
RFC-2: MCP resource-level read-only endpoints
Add MCP Resource definitions for run://{run_id}, control://{id}, etc. to expose read-only data without multiple tool calls.
RFC-GH-wafpass-mcp-6
RFC-4: Multi-step remediation plans (apply with rollback)
Extend auto-fix/classify with an apply step that records changes and supports rollback.
RFC-GH-wafpass-mcp-5
RFC-3: Streaming/paginated tool results for large runs
Add cursor-based pagination helpers so large runs do not blow MCP message size limits.
RFC-GH-wafpass-mcp-3
RFC-1: Auto-fix default templates for WOMBATpass controls
Add fix blocks to control YAMLs or a central provider registry so common assertions get default patches.
MCP · Ouvertes à la relecture
RFC-GH-wafpass-mcp-7
RFC-5: Role-aware natural tool aliasing
Allow curated aliases for long auto-generated MCP tool names so LLMs can match them more naturally.
RFC-GH-wafpass-mcp-4
RFC-2: MCP resource-level read-only endpoints
Add MCP Resource definitions for run://{run_id}, control://{id}, etc. to expose read-only data without multiple tool calls.
RFC-GH-wafpass-mcp-6
RFC-4: Multi-step remediation plans (apply with rollback)
Extend auto-fix/classify with an apply step that records changes and supports rollback.
RFC-GH-wafpass-mcp-5
RFC-3: Streaming/paginated tool results for large runs
Add cursor-based pagination helpers so large runs do not blow MCP message size limits.
RFC-GH-wafpass-mcp-3
RFC-1: Auto-fix default templates for WOMBATpass controls
Add fix blocks to control YAMLs or a central provider registry so common assertions get default patches.
Framework
RFC-0001
Initial 7-pillar framework structure
Establishes the core seven-pillar model as the foundational structure of Wombat. Extended to eight pillars by RFC-0012.
RFC-0002
Public 2026 roadmap and milestone planning
Defines the public roadmap for 2026 covering Q1–Q4 milestones, v1.0 target, pilot programme, and foundation readiness goals.
RFC-0003
Pillar descriptions and key questions — 7 pillars
Adds the initial content definition for each of the 7 pillars. Later extended to cover the 8th Agentic pillar (RFC-0012).
RFC-0004
Documentation migration to AsciiDoc / Antora
Migrates all framework documentation from Markdown to AsciiDoc and establishes Antora as the documentation build system with component versioning.
RFC-0005
Contribution metadata — CONTRIBUTING, CODE_OF_CONDUCT, SECURITY
Adds the standard open-source health files to the framework repository.
RFC-0006
Sovereign pillar (Pillar 7) — initial controls
Introduces the Sovereign pillar as the 7th pillar of Wombat with 10 initial controls (WAF-SOV-010 through WAF-SOV-100).
RFC-0007
Governance refactor — modular best practices, case studies and navigation
Restructures the Governance pillar into modular best-practice pages and adds case-study content.
RFC-0008
Controls schema v1 — machine-readable YAML specification
Defines a formal schema for Wombat controls YAML files, enabling validation and tooling integration for the 83+ controls library.
RFC-0009
PASS scoring model — formal specification for v1.0
Formalises the PASS scoring model as a normative specification for tier definitions, calculation rules, aggregation logic, and versioning contract.
RFC-0010
Assessment tooling — CLI and scorecard approach
Defines the approach for official Wombat assessment tooling including the WOMBATpass CLI, server, dashboard, and web scorecard.
RFC-0011
CI/CD pipeline for framework and tooling repositories
Introduces automated checks and release workflows for framework, wafpass-core, wafpass-server, and wafpass-dashboard repositories.
RFC-0012
Agentic pillar as the 8th pillar
Adds the Agentic pillar as the 8th pillar of Wombat with 10 initial controls, regulatory mappings, and bilingual documentation.
RFC-0016
Control-level remediation playbooks
Standardises machine- and human-readable remediation guidance for every Wombat control so operators can act on findings directly.
RFC-0017
Multi-cloud provider expansion beyond AWS and SINA Cloud
Defines how WOMBATpass detection and controls will be extended to cover Azure, GCP, and other cloud providers while keeping the framework cloud-agnostic.
RFC-GH-framework-26
RFC: Quality Assurance
CI checks for dead xrefs, unregistered nav.adoc files, and control-schema consistency between YAML, AsciiDoc, and navigation.
RFC-GH-framework-25
RFC: Expand Sovereign & Resources
Expand Sovereign definitions, evidence matrix, and create real overview/glossary pages for resources and wording.
RFC-GH-framework-23
RFC: Complete the Agentic Pillar
Complete Agentic pillar maturity, evidence, glossary, and best-practice pages with examples.
RFC-GH-framework-22
RFC: Consolidate Navigation & Links
Standardise module links, convert relative xrefs to module-prefixed xrefs, and clean Markdown links.
RFC-GH-framework-21
RFC: Finalize Antora Structure
Finalise antora.yml registration, create pillar-security nav, update README/AGENTS for 8-module layout.
RFC-GH-framework-24
RFC: Correct and Expand the Controls Catalog
Align controls to 8 pillars, add Agentic, and extend control-schema.adoc.
Core
RFC-0013
WOMBATpass support for Pillar-8 Agentic
Extends WOMBATpass CLI, server, and dashboard to evaluate the Agentic pillar controls as part of a full PASS assessment.
RFC-0014
WOMBATpass CLI / Server / Dashboard v1.1.0 release
Releases WOMBATpass CLI v1.1.0, Server v1.1.0, and Dashboard v1.1.0 with Pillar-8 Agentic support, detection fixes, and SINA Cloud region detection.
RFC-GH-wafpass-core-41
Feature Request: Comprehensive Test/Quality Coverage Implementation Plan
Unify fragmented test and coverage strategy across wafpass-core, server, and dashboard.
RFC-GH-wafpass-core-42
Feature Request: API Versioning and Backwards-Compatibility Strategy for WOMBATpass
Define API maturity, backwards-compatibility rules, and versioning strategy for WOMBATpass APIs.
RFC-GH-wafpass-core-43
Feature Request: Source Snapshots — Ingestion Contract and Reliable Upload Path
Define a reliable source-snapshot ingestion contract so dashboard preview and auto-fix work consistently.
RFC-GH-wafpass-core-40
Feature Request: Dashboard UX Overhaul — Guided Onboarding, Role-Based Landing, and Progressive Disclosure
Reduce dashboard navigation fragmentation and add guided onboarding with role-based landing pages.
RFC-GH-wafpass-core-39
Feature Request: Implement Action-Oriented Notifications
Make dashboard notifications actionable instead of passive text displays.
RFC-GH-wafpass-core-38
Feature Request: Implement Control Packs Marketplace
Expand the control-packs feature beyond admin-only uploads to a real marketplace with discovery and governance.
RFC-GH-wafpass-core-37
Feature Request: Implement Maturity-Tier Enforcement Policy Gates
Tie maturity tiers to CI/CD policy gates so pipelines can block promotion below a target tier.
MCP
RFC-GH-wafpass-mcp-7
RFC-5: Role-aware natural tool aliasing
Allow curated aliases for long auto-generated MCP tool names so LLMs can match them more naturally.
RFC-GH-wafpass-mcp-4
RFC-2: MCP resource-level read-only endpoints
Add MCP Resource definitions for run://{run_id}, control://{id}, etc. to expose read-only data without multiple tool calls.
RFC-GH-wafpass-mcp-6
RFC-4: Multi-step remediation plans (apply with rollback)
Extend auto-fix/classify with an apply step that records changes and supports rollback.
RFC-GH-wafpass-mcp-5
RFC-3: Streaming/paginated tool results for large runs
Add cursor-based pagination helpers so large runs do not blow MCP message size limits.
RFC-GH-wafpass-mcp-3
RFC-1: Auto-fix default templates for WOMBATpass controls
Add fix blocks to control YAMLs or a central provider registry so common assertions get default patches.
Framework
RFC-0015
Website radical redesign — apply dark-first theme to all public pages
Applies the radical dark-first design system to the remaining public pages so the whole site uses one consistent visual language.
MCP
RFC-GH-wafpass-mcp-7
RFC-5: Role-aware natural tool aliasing
Allow curated aliases for long auto-generated MCP tool names so LLMs can match them more naturally.
RFC-GH-wafpass-mcp-4
RFC-2: MCP resource-level read-only endpoints
Add MCP Resource definitions for run://{run_id}, control://{id}, etc. to expose read-only data without multiple tool calls.
RFC-GH-wafpass-mcp-6
RFC-4: Multi-step remediation plans (apply with rollback)
Extend auto-fix/classify with an apply step that records changes and supports rollback.
RFC-GH-wafpass-mcp-5
RFC-3: Streaming/paginated tool results for large runs
Add cursor-based pagination helpers so large runs do not blow MCP message size limits.
RFC-GH-wafpass-mcp-3
RFC-1: Auto-fix default templates for WOMBATpass controls
Add fix blocks to control YAMLs or a central provider registry so common assertions get default patches.
Framework
RFC-GH-framework-26
RFC: Quality Assurance
CI checks for dead xrefs, unregistered nav.adoc files, and control-schema consistency between YAML, AsciiDoc, and navigation.
RFC-GH-framework-25
RFC: Expand Sovereign & Resources
Expand Sovereign definitions, evidence matrix, and create real overview/glossary pages for resources and wording.
RFC-GH-framework-23
RFC: Complete the Agentic Pillar
Complete Agentic pillar maturity, evidence, glossary, and best-practice pages with examples.
RFC-GH-framework-22
RFC: Consolidate Navigation & Links
Standardise module links, convert relative xrefs to module-prefixed xrefs, and clean Markdown links.
RFC-GH-framework-21
RFC: Finalize Antora Structure
Finalise antora.yml registration, create pillar-security nav, update README/AGENTS for 8-module layout.
RFC-GH-framework-24
RFC: Correct and Expand the Controls Catalog
Align controls to 8 pillars, add Agentic, and extend control-schema.adoc.
Core
RFC-GH-wafpass-core-41
Feature Request: Comprehensive Test/Quality Coverage Implementation Plan
Unify fragmented test and coverage strategy across wafpass-core, server, and dashboard.
RFC-GH-wafpass-core-42
Feature Request: API Versioning and Backwards-Compatibility Strategy for WOMBATpass
Define API maturity, backwards-compatibility rules, and versioning strategy for WOMBATpass APIs.
RFC-GH-wafpass-core-43
Feature Request: Source Snapshots — Ingestion Contract and Reliable Upload Path
Define a reliable source-snapshot ingestion contract so dashboard preview and auto-fix work consistently.
RFC-GH-wafpass-core-40
Feature Request: Dashboard UX Overhaul — Guided Onboarding, Role-Based Landing, and Progressive Disclosure
Reduce dashboard navigation fragmentation and add guided onboarding with role-based landing pages.
RFC-GH-wafpass-core-39
Feature Request: Implement Action-Oriented Notifications
Make dashboard notifications actionable instead of passive text displays.
RFC-GH-wafpass-core-38
Feature Request: Implement Control Packs Marketplace
Expand the control-packs feature beyond admin-only uploads to a real marketplace with discovery and governance.
RFC-GH-wafpass-core-37
Feature Request: Implement Maturity-Tier Enforcement Policy Gates
Tie maturity tiers to CI/CD policy gates so pipelines can block promotion below a target tier.
Framework
RFC-0016
Control-level remediation playbooks
Standardises machine- and human-readable remediation guidance for every Wombat control so operators can act on findings directly.
RFC-0017
Multi-cloud provider expansion beyond AWS and SINA Cloud
Defines how WOMBATpass detection and controls will be extended to cover Azure, GCP, and other cloud providers while keeping the framework cloud-agnostic.
Framework
RFC-0001
Initial 7-pillar framework structure
Establishes the core seven-pillar model as the foundational structure of Wombat. Extended to eight pillars by RFC-0012.
RFC-0002
Public 2026 roadmap and milestone planning
Defines the public roadmap for 2026 covering Q1–Q4 milestones, v1.0 target, pilot programme, and foundation readiness goals.
RFC-0003
Pillar descriptions and key questions — 7 pillars
Adds the initial content definition for each of the 7 pillars. Later extended to cover the 8th Agentic pillar (RFC-0012).
RFC-0004
Documentation migration to AsciiDoc / Antora
Migrates all framework documentation from Markdown to AsciiDoc and establishes Antora as the documentation build system with component versioning.
RFC-0005
Contribution metadata — CONTRIBUTING, CODE_OF_CONDUCT, SECURITY
Adds the standard open-source health files to the framework repository.
RFC-0006
Sovereign pillar (Pillar 7) — initial controls
Introduces the Sovereign pillar as the 7th pillar of Wombat with 10 initial controls (WAF-SOV-010 through WAF-SOV-100).
RFC-0007
Governance refactor — modular best practices, case studies and navigation
Restructures the Governance pillar into modular best-practice pages and adds case-study content.
RFC-0008
Controls schema v1 — machine-readable YAML specification
Defines a formal schema for Wombat controls YAML files, enabling validation and tooling integration for the 83+ controls library.
RFC-0009
PASS scoring model — formal specification for v1.0
Formalises the PASS scoring model as a normative specification for tier definitions, calculation rules, aggregation logic, and versioning contract.
RFC-0010
Assessment tooling — CLI and scorecard approach
Defines the approach for official Wombat assessment tooling including the WOMBATpass CLI, server, dashboard, and web scorecard.
RFC-0011
CI/CD pipeline for framework and tooling repositories
Introduces automated checks and release workflows for framework, wafpass-core, wafpass-server, and wafpass-dashboard repositories.
RFC-0012
Agentic pillar as the 8th pillar
Adds the Agentic pillar as the 8th pillar of Wombat with 10 initial controls, regulatory mappings, and bilingual documentation.
Core
RFC-0013
WOMBATpass support for Pillar-8 Agentic
Extends WOMBATpass CLI, server, and dashboard to evaluate the Agentic pillar controls as part of a full PASS assessment.
RFC-0014
WOMBATpass CLI / Server / Dashboard v1.1.0 release
Releases WOMBATpass CLI v1.1.0, Server v1.1.0, and Dashboard v1.1.0 with Pillar-8 Agentic support, detection fixes, and SINA Cloud region detection.
Envie de proposer un changement ?
Ouvrez une discussion GitHub avec le modèle de RFC. La communauté la relit, les mainteneurs décident, tout est documenté et traçable.
Architecture Decision Records.
Les ADR consignent les décisions structurelles et transverses qui façonnent l'écosystème Wombat, ses dépôts et ses contrats.
ADR-000
Wombat Federated Repository Architecture & Onboarding Overview
Master onboarding document explaining the Wombat ecosystem, repository layout, two-branch documentation model, and central wafpass-result.json contract.
ADR-001
The wafpass-result.json Contract
Defines the single JSON schema that all Wombat components use to exchange scan results, findings, waivers, risks, and metadata.
ADR-002
Two Long-Lived Branches for German and English Framework Documentation
Uses main-de and main-en branches (checked out as framework/ and framework-en/) so German and English Antora component releases can evolve independently.
ADR-000
Wombat Federated Repository Architecture & Onboarding Overview
Master onboarding document explaining the Wombat ecosystem, repository layout, two-branch documentation model, and central wafpass-result.json contract.
ADR-001
The wafpass-result.json Contract
Defines the single JSON schema that all Wombat components use to exchange scan results, findings, waivers, risks, and metadata.
ADR-002
Two Long-Lived Branches for German and English Framework Documentation
Uses main-de and main-en branches (checked out as framework/ and framework-en/) so German and English Antora component releases can evolve independently.
Registre des décisions lisible par machine
Toutes les RFC et tous les ADR sont aussi disponibles dans un fichier YAML unique que les outils, scripts et systèmes en aval peuvent analyser. Le registre comprend les statuts, catégories, dépôts, tags et liens directs vers chaque entrée.
Qu'est-ce qui justifie une RFC ?
Tous les changements n'exigent pas une RFC, seulement les plus importants. Utilisez le tableau ci-dessous pour décider.
| Type de changement | RFC nécessaire ? | Processus |
|---|---|---|
| Nouveau pilier ou suppression d'un pilier | Oui | RFC → vote du TSC → PR |
| Changements du modèle de scoring (niveaux PASS, pondérations) | Oui | RFC → vote du TSC → PR |
| Changement incompatible du schéma ou des ID des contrôles | Oui | RFC → vote du TSC → PR |
| Proposition d'un nouveau groupe de travail | Oui | RFC → lazy consensus → charte publiée |
| Changements de gouvernance ou de rôles | Oui | RFC → majorité qualifiée du TSC |
| Nouveau contrôle (compatible, additif) | Recommandé | PR avec lien vers la discussion, lazy consensus |
| Formulations de la documentation, coquilles, traductions | Non | PR uniquement |
| Contenu du site web, articles de blog | Non | PR uniquement |
Cycle de statut d'une RFC.
Chaque RFC suit le même parcours documenté, du premier brouillon à la décision finale.
Bien rédiger une RFC.
Trois éléments qui font la différence entre une RFC qui avance vite et une RFC qui stagne.
Exposez le problème, pas la solution
Commencez par ce qui est cassé ou manquant, pas par ce que vous voulez construire. Les relecteurs doivent s'accorder sur la réalité du problème avant d'évaluer votre solution. Expliquez le « pourquoi » avant le « quoi ».
Montrez les compromis et les alternatives
Une bonne RFC explique ce qui a été envisagé d'autre et pourquoi cela a été écarté. Cela évite des cycles de relecture et donne du contexte aux futurs mainteneurs lorsque la personne autrice n'est plus là.
Soyez précis sur l'impact
Qui est concerné ? Quels dépôts, fichiers ou contrats publics changent ? Plus le périmètre est clair, plus vite la communauté peut donner un retour utile et un mainteneur trancher.
Façonnez la prochaine décision.
Choisissez une RFC ouverte, partagez votre point de vue ou ouvrez-en une nouvelle. Le framework se construit en public et chaque voix compte.