Kuadrant/architecture is a repository for cross-cutting architecture documents and design proposals that affect multiple components within the Kuadrant API management platform.
The repository serves as a centralized location for documenting architectural decisions and design patterns that span across Kuadrant's control plane and data plane. It hosts the RFC (Request For Comments) process, which provides a structured mechanism for proposing and discussing changes that impact end-user experience. The RFC workflow requires that any modifications to APIs, behavioral changes, or new features undergo community review and consensus before implementation begins, while routine work like bug fixes, refactoring, and performance improvements proceed through standard pull requests to individual component repositories.
Teams adopting this repository should understand that it functions as a governance and documentation hub rather than a code repository. It is most relevant for contributors and maintainers working on Kuadrant's core platform who need to propose changes affecting multiple components or the overall system architecture. Organizations evaluating Kuadrant should review the architecture documents here to understand the platform's design philosophy and planned evolution. The RFC process ensures that significant changes receive broad stakeholder input before development begins, which can slow feature velocity but increases confidence in architectural decisions.
The project maintains architecture documentation as a living resource, with the README noting that the repository is actively being updated. Development activity centers on RFC submissions and architectural discussions rather than code commits, reflecting the repository's role as a design-stage artifact. The project distinguishes between changes requiring RFC approval and those that do not, establishing clear criteria for when community review is necessary versus when standard development workflows suffice.
