Governance · Transparent by default

RFC Tracker

Every significant change to WAF++ starts with a public Request for Comments. This page tracks every RFC — from first draft to merge — so every decision stays traceable.

14 implemented 1 open for review 2 drafts
17
Total RFCs
1
Open for review
2
Drafts
14
Implemented
0
Accepted
0
Rejected
Proposals

All Requests for Comments

Filter by status, read the summaries, and follow the linked discussions and pull requests.

RFC-0001 Initial 7-pillar framework structure
implemented framework

Establishes the core seven-pillar model as the foundational structure of WAF++, covering Security, Reliability, Performance Efficiency, Cost Optimisation, Operational Excellence, Sustainability, and Developer Experience. Extended to eight pillars by RFC-0012.

Author: sascha-lewandowski Opened: 2025-12-05Decided: 2025-12-05Implemented: 2025-12-05PR: #1
RFC-0002 Public 2026 roadmap and milestone planning
implemented governance

Defines the public roadmap for 2026 covering Q1–Q4 milestones, including v1.0 target, pilot programme, and foundation readiness goals.

Author: sascha-lewandowski Opened: 2025-12-06Decided: 2025-12-06Implemented: 2025-12-06PR: #2
RFC-0003 Pillar descriptions and key questions — 7 pillars
implemented framework

Adds the initial content definition for each of the 7 pillars: scope, rationale, and key assessment questions. Serves as the baseline for the controls library and was later extended to cover the 8th Agentic pillar (RFC-0012).

Author: sascha-lewandowski Opened: 2025-12-07Decided: 2025-12-07Implemented: 2025-12-07PR: #3
RFC-0004 Documentation migration to AsciiDoc / Antora
implemented docs

Migrates all framework documentation from Markdown to AsciiDoc and establishes Antora as the documentation build system with component versioning (v1.0).

Author: t1murl Opened: 2026-02-20Decided: 2026-02-26Implemented: 2026-02-26PR: #4
RFC-0005 Contribution metadata: CONTRIBUTING, CODE_OF_CONDUCT, SECURITY
implemented governance

Adds the standard open-source health files to the framework repository: contribution guidelines, code of conduct (based on Contributor Covenant v2.1), and security policy.

Author: sascha-lewandowski Opened: 2026-02-06Decided: 2026-02-08Implemented: 2026-02-08PR: #6
RFC-0006 Sovereign pillar (Pillar 7) — initial controls
implemented framework

Introduces the Sovereign pillar as the 7th pillar of WAF++, covering data sovereignty, compliance, and jurisdictional control. Ships with 10 initial controls (WAF-SOV-010 through WAF-SOV-100).

Author: sascha-lewandowski Opened: 2026-02-14Decided: 2026-03-04Implemented: 2026-03-04
RFC-0007 Governance refactor: modular best practices, case studies and navigation
implemented framework

Restructures the Governance pillar (Pillar 7) into modular best-practice pages, adds case-study content, and updates the Antora navigation to improve discoverability and readability.

Author: sascha-lewandowski Opened: 2026-02-24Decided: 2026-03-04Implemented: 2026-03-04PR: #10
RFC-0008 Controls schema v1 — machine-readable YAML specification
implemented tooling

Defines a formal schema for WAF++ controls YAML files, enabling consistent validation, tooling integration, and third-party consumption of the 83+ controls library. Shipped as part of the v1.0 release.

Author: sascha-lewandowski Opened: 2026-03-10Decided: 2026-05-12Implemented: 2026-05-12
RFC-0009 PASS scoring model — formal specification for v1.0
implemented framework

Formalises the PASS scoring model as a normative specification: tier definitions, calculation rules, aggregation logic, and versioning contract. Required for and shipped with the WAFPass CLI / Server v1.0.0 release.

Author: t1murl Opened: 2026-03-08Decided: 2026-05-12Implemented: 2026-05-12
RFC-0010 Assessment tooling — CLI and scorecard approach
implemented tooling

Defines the approach for official WAF++ assessment tooling: the WAFPass CLI, server, dashboard, and web scorecard that consume the controls library and produce a PASS score report. Shipped with WAFPass v1.0.0 and extended in v1.1.0.

Author: sascha-lewandowski Opened: 2026-03-11Decided: 2026-05-12Implemented: 2026-05-12
RFC-0011 CI/CD pipeline for framework and tooling repositories
implemented tooling

Introduces automated checks and release workflows for the framework, pass, wafpass-server, and wafpass-dashboard repositories: Antora build validation, controls YAML linting, release automation, and link checking on every pull request.

Author: t1murl Opened: 2026-03-11Decided: 2026-03-22Implemented: 2026-03-22
RFC-0012 Agentic pillar as the 8th pillar
implemented framework

Adds the Agentic pillar (WAF-AGN) as the 8th pillar of WAF++, covering autonomous AI agent governance. Ships with 10 initial controls (WAF-AGN-010 through WAF-AGN-100), regulatory mappings, and English and German documentation. Brings the framework to 8 pillars and 83+ controls.

Author: sascha-lewandowski Opened: 2026-07-01Decided: 2026-07-05Implemented: 2026-07-05PR: #19
RFC-0013 WAFPass support for Pillar-8 Agentic
implemented tooling

Extends WAFPass CLI, server, and dashboard to evaluate the Agentic pillar controls (WAF-AGN-*) as part of a full PASS assessment. Merged ahead of the WAFPass v1.1.0 release.

Author: sascha-lewandowski Opened: 2026-05-20Decided: 2026-05-27Implemented: 2026-05-27PR: #28
RFC-0014 WAFPass CLI / Server / Dashboard v1.1.0 release
implemented tooling

Releases WAFPass CLI v1.1.0, WAFPass Server v1.1.0, and WAFPass Dashboard v1.1.0 with Pillar-8 Agentic support, detection fixes, and SINA Cloud region detection. Aligned with framework v1.1 and the 83+ controls library.

Author: sascha-lewandowski Opened: 2026-06-28Decided: 2026-07-05Implemented: 2026-07-05PR: #31
RFC-0015 Website radical redesign — apply dark-first theme to all public pages
open docs

Applies the radical dark-first design system to the remaining public pages (RFC tracker, team, roles, about, press, install) so the whole site uses one consistent visual language and accessibility patterns.

Author: sascha-lewandowski Opened: 2026-07-06Discussion: GitHub →
RFC-0016 Control-level remediation playbooks
draft framework

Standardises machine- and human-readable remediation guidance for every WAF++ control so operators can act on findings directly from a PASS report or dashboard.

Author: sascha-lewandowski Opened: 2026-07-08
RFC-0017 Multi-cloud provider expansion beyond AWS and SINA Cloud
draft tooling

Defines how WAFPass detection and controls will be extended to cover Azure, GCP, and other cloud providers while keeping the framework cloud-agnostic.

Author: sascha-lewandowski Opened: 2026-07-08
RFC-0015 Website radical redesign — apply dark-first theme to all public pages
open docs

Applies the radical dark-first design system to the remaining public pages (RFC tracker, team, roles, about, press, install) so the whole site uses one consistent visual language and accessibility patterns.

Author: sascha-lewandowski Opened: 2026-07-06Discussion: GitHub →
RFC-0016 Control-level remediation playbooks
draft framework

Standardises machine- and human-readable remediation guidance for every WAF++ control so operators can act on findings directly from a PASS report or dashboard.

Author: sascha-lewandowski Opened: 2026-07-08
RFC-0017 Multi-cloud provider expansion beyond AWS and SINA Cloud
draft tooling

Defines how WAFPass detection and controls will be extended to cover Azure, GCP, and other cloud providers while keeping the framework cloud-agnostic.

Author: sascha-lewandowski Opened: 2026-07-08
RFC-0001 Initial 7-pillar framework structure
implemented framework

Establishes the core seven-pillar model as the foundational structure of WAF++, covering Security, Reliability, Performance Efficiency, Cost Optimisation, Operational Excellence, Sustainability, and Developer Experience. Extended to eight pillars by RFC-0012.

Author: sascha-lewandowski Opened: 2025-12-05Decided: 2025-12-05Implemented: 2025-12-05PR: #1
RFC-0002 Public 2026 roadmap and milestone planning
implemented governance

Defines the public roadmap for 2026 covering Q1–Q4 milestones, including v1.0 target, pilot programme, and foundation readiness goals.

Author: sascha-lewandowski Opened: 2025-12-06Decided: 2025-12-06Implemented: 2025-12-06PR: #2
RFC-0003 Pillar descriptions and key questions — 7 pillars
implemented framework

Adds the initial content definition for each of the 7 pillars: scope, rationale, and key assessment questions. Serves as the baseline for the controls library and was later extended to cover the 8th Agentic pillar (RFC-0012).

Author: sascha-lewandowski Opened: 2025-12-07Decided: 2025-12-07Implemented: 2025-12-07PR: #3
RFC-0004 Documentation migration to AsciiDoc / Antora
implemented docs

Migrates all framework documentation from Markdown to AsciiDoc and establishes Antora as the documentation build system with component versioning (v1.0).

Author: t1murl Opened: 2026-02-20Decided: 2026-02-26Implemented: 2026-02-26PR: #4
RFC-0005 Contribution metadata: CONTRIBUTING, CODE_OF_CONDUCT, SECURITY
implemented governance

Adds the standard open-source health files to the framework repository: contribution guidelines, code of conduct (based on Contributor Covenant v2.1), and security policy.

Author: sascha-lewandowski Opened: 2026-02-06Decided: 2026-02-08Implemented: 2026-02-08PR: #6
RFC-0006 Sovereign pillar (Pillar 7) — initial controls
implemented framework

Introduces the Sovereign pillar as the 7th pillar of WAF++, covering data sovereignty, compliance, and jurisdictional control. Ships with 10 initial controls (WAF-SOV-010 through WAF-SOV-100).

Author: sascha-lewandowski Opened: 2026-02-14Decided: 2026-03-04Implemented: 2026-03-04
RFC-0007 Governance refactor: modular best practices, case studies and navigation
implemented framework

Restructures the Governance pillar (Pillar 7) into modular best-practice pages, adds case-study content, and updates the Antora navigation to improve discoverability and readability.

Author: sascha-lewandowski Opened: 2026-02-24Decided: 2026-03-04Implemented: 2026-03-04PR: #10
RFC-0008 Controls schema v1 — machine-readable YAML specification
implemented tooling

Defines a formal schema for WAF++ controls YAML files, enabling consistent validation, tooling integration, and third-party consumption of the 83+ controls library. Shipped as part of the v1.0 release.

Author: sascha-lewandowski Opened: 2026-03-10Decided: 2026-05-12Implemented: 2026-05-12
RFC-0009 PASS scoring model — formal specification for v1.0
implemented framework

Formalises the PASS scoring model as a normative specification: tier definitions, calculation rules, aggregation logic, and versioning contract. Required for and shipped with the WAFPass CLI / Server v1.0.0 release.

Author: t1murl Opened: 2026-03-08Decided: 2026-05-12Implemented: 2026-05-12
RFC-0010 Assessment tooling — CLI and scorecard approach
implemented tooling

Defines the approach for official WAF++ assessment tooling: the WAFPass CLI, server, dashboard, and web scorecard that consume the controls library and produce a PASS score report. Shipped with WAFPass v1.0.0 and extended in v1.1.0.

Author: sascha-lewandowski Opened: 2026-03-11Decided: 2026-05-12Implemented: 2026-05-12
RFC-0011 CI/CD pipeline for framework and tooling repositories
implemented tooling

Introduces automated checks and release workflows for the framework, pass, wafpass-server, and wafpass-dashboard repositories: Antora build validation, controls YAML linting, release automation, and link checking on every pull request.

Author: t1murl Opened: 2026-03-11Decided: 2026-03-22Implemented: 2026-03-22
RFC-0012 Agentic pillar as the 8th pillar
implemented framework

Adds the Agentic pillar (WAF-AGN) as the 8th pillar of WAF++, covering autonomous AI agent governance. Ships with 10 initial controls (WAF-AGN-010 through WAF-AGN-100), regulatory mappings, and English and German documentation. Brings the framework to 8 pillars and 83+ controls.

Author: sascha-lewandowski Opened: 2026-07-01Decided: 2026-07-05Implemented: 2026-07-05PR: #19
RFC-0013 WAFPass support for Pillar-8 Agentic
implemented tooling

Extends WAFPass CLI, server, and dashboard to evaluate the Agentic pillar controls (WAF-AGN-*) as part of a full PASS assessment. Merged ahead of the WAFPass v1.1.0 release.

Author: sascha-lewandowski Opened: 2026-05-20Decided: 2026-05-27Implemented: 2026-05-27PR: #28
RFC-0014 WAFPass CLI / Server / Dashboard v1.1.0 release
implemented tooling

Releases WAFPass CLI v1.1.0, WAFPass Server v1.1.0, and WAFPass Dashboard v1.1.0 with Pillar-8 Agentic support, detection fixes, and SINA Cloud region detection. Aligned with framework v1.1 and the 83+ controls library.

Author: sascha-lewandowski Opened: 2026-06-28Decided: 2026-07-05Implemented: 2026-07-05PR: #31

Want to propose a change?

Open a GitHub Discussion using the RFC template. The community reviews it, maintainers decide — everything is documented and traceable.

Process

What qualifies as an RFC?

Not every change needs an RFC — only significant ones. Use the table below to decide.

Change type RFC needed? Process
New pillar or removal of a pillar Yes RFC → TSC vote → PR
Scoring model changes (PASS tiers, weights) Yes RFC → TSC vote → PR
Breaking change to controls schema or IDs Yes RFC → TSC vote → PR
New Working Group proposal Yes RFC → lazy consensus → charter published
Governance or role changes Yes RFC → TSC supermajority
New control (non-breaking, additive) Recommended PR with discussion link · lazy consensus
Docs wording, typo fixes, translations No PR only
Website content, blog posts No PR only
Lifecycle

RFC status flow

Every RFC follows the same documented path — from first draft to closed decision.

draft
Author writes the proposal in GitHub Discussions
open
Minimum 5 business days open for community comment
accepted
TSC vote or lazy consensus — documented publicly
implemented
PR merged, changelog entry added, RFC closed
Alternative outcomes: rejected (not accepted after review)  ·  withdrawn (pulled by author). Both are documented with reasons.
Writing an RFC

How to write a good RFC

Three things that make the difference between an RFC that moves fast and one that stalls.

State the problem, not the solution

Start with what is broken or missing — not with what you want to build. Reviewers need to agree that the problem is real before they can evaluate your proposed solution. Frame the "why" before the "what".

Document trade-offs explicitly

Every decision has costs. Name them. What gets worse? What are the alternatives you considered? An RFC that acknowledges trade-offs earns trust faster than one that only sells the upside.

Link to evidence

Point to real examples — issues, incidents, prior discussions, or production patterns. Evidence turns opinions into traceable facts and dramatically shortens the review cycle.

Ready to contribute?

Start an RFC today.

Open a discussion on GitHub, follow the template, and let the process do the rest. No prior approval needed — just a clear problem statement.