Öffentlich entwickelt.
Jede wesentliche Änderung an Wombat beginnt mit einem öffentlichen Request for Comments oder Architecture Decision Record. Diese Seite verfolgt jede Entscheidung vom ersten Entwurf bis zum Merge — nichts bleibt verborgen.
Alle Requests for Comments.
Filtern Sie nach Projekt und Status, lesen Sie die Zusammenfassungen und folgen Sie den verlinkten Diskussionen und Pull Requests.
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 · Offen zur Prüfung
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 · Entwürfe
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 · Entschieden / umgesetzt
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 · Offen zur Prüfung
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 · Entschieden / umgesetzt
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 · Offen zur Prüfung
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.
Sie möchten eine Änderung vorschlagen?
Eröffnen Sie eine GitHub-Diskussion mit der RFC-Vorlage. Die Community prüft sie, die Maintainer entscheiden, alles wird dokumentiert und ist nachvollziehbar.
Architecture Decision Records.
ADRs halten die strukturellen und übergreifenden Entscheidungen fest, die das Wombat-Ökosystem, seine Repositories und Verträge prägen.
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.
Maschinenlesbares Entscheidungsregister
Alle RFCs und ADRs stehen auch als einzelne YAML-Datei bereit, die Tools, Skripte und nachgelagerte Systeme auswerten können. Das Register enthält Status, Kategorien, Repositories, Tags und direkte Links zu jedem Eintrag.
Was ist ein Fall für einen RFC?
Nicht jede Änderung braucht einen RFC, nur wesentliche. Die Tabelle unten hilft bei der Entscheidung.
| Art der Änderung | RFC nötig? | Prozess |
|---|---|---|
| Neue Säule oder Entfernen einer Säule | Ja | RFC → TSC-Abstimmung → PR |
| Änderungen am Scoring-Modell (PASS-Stufen, Gewichtungen) | Ja | RFC → TSC-Abstimmung → PR |
| Breaking Change am Controls-Schema oder an IDs | Ja | RFC → TSC-Abstimmung → PR |
| Vorschlag für eine neue Working Group | Ja | RFC → Lazy Consensus → Charta veröffentlicht |
| Änderungen an Governance oder Rollen | Ja | RFC → qualifizierte TSC-Mehrheit |
| Neuer Control (nicht breaking, ergänzend) | Empfohlen | PR mit Link zur Diskussion, Lazy Consensus |
| Formulierungen in der Doku, Tippfehler, Übersetzungen | Nein | Nur PR |
| Website-Inhalte, Blogartikel | Nein | Nur PR |
Status-Ablauf eines RFC.
Jeder RFC folgt demselben dokumentierten Weg, vom ersten Entwurf bis zur abgeschlossenen Entscheidung.
So schreiben Sie einen guten RFC.
Drei Dinge, die den Unterschied machen zwischen einem RFC, der schnell vorankommt, und einem, der ins Stocken gerät.
Beschreiben Sie das Problem, nicht die Lösung
Beginnen Sie mit dem, was kaputt ist oder fehlt, nicht mit dem, was Sie bauen wollen. Reviewer müssen sich einig sein, dass das Problem real ist, bevor sie Ihren Lösungsvorschlag bewerten können. Klären Sie das „Warum“ vor dem „Was“.
Zeigen Sie Abwägungen und Alternativen
Ein starker RFC erklärt, was sonst noch erwogen und warum es verworfen wurde. Das spart Review-Runden und gibt künftigen Maintainern Kontext, wenn die ursprüngliche autorisierende Person nicht mehr dabei ist.
Seien Sie konkret bei den Auswirkungen
Wer ist betroffen? Welche Repositories, Dateien oder öffentlichen Verträge ändern sich? Je klarer der Umfang, desto schneller kann die Community nützliches Feedback geben und ein Maintainer entscheiden.
Gestalten Sie die nächste Entscheidung mit.
Wählen Sie einen offenen RFC, teilen Sie Ihre Sicht oder eröffnen Sie einen neuen. Das Framework entsteht öffentlich, und jede Stimme zählt.