This phase defines how the implementation of LUNA Charts is governed to ensure long-term architectural consistency, product quality, and maintainability.
Rather than introducing new architectural decisions, Implementation Governance ensures that all implementation activities remain aligned with the architecture defined in previous phases. It establishes responsibilities, review processes, quality gates, and decision-making procedures for both contributors and maintainers.
As an open-source project, LUNA Charts balances community contributions with centralized architectural governance to protect the project's long-term vision.
Implementation Governance is guided by the following principles:
The community contributes ideas and implementation proposals.
Responsibilities include:
The community may influence discussions but does not make architectural decisions.
Contributors actively improve the project.
Responsibilities include:
All contributions are subject to review before integration.
The Maintainer Team is responsible for the long-term integrity of the project.
Responsibilities include:
Architectural governance is owned collectively by the Maintainer Team rather than by an individual contributor.
Implementation Governance operates across three complementary layers.
Objective quality checks performed automatically during development.
Examples include:
These checks ensure that objective quality requirements are consistently enforced.
Architectural Governance ensures that implementations remain aligned with the defined architecture.
Maintainers review topics such as:
Architectural compliance cannot be verified solely through automation and therefore requires human review.
Project Governance focuses on overall software quality beyond technical correctness.
Evaluation criteria include:
A contribution may therefore be rejected even if all automated quality checks have passed.
Every contribution is evaluated against the documented architecture.
A Pull Request may be rejected if it:
Maintainers are responsible for ensuring compliance before accepting contributions.
Architectural evolution follows a structured review process.
Proposal
↓
Architecture Discussion
↓
Maintainer Review
↓
Decision
↓
Architecture Documentation Update
↓
Evolution Note
↓
Implementation
Architectural decisions become official only after the architecture documentation has been updated.
Implementation follows the documented architecture rather than defining it.
Public releases require successful completion of all mandatory quality gates defined by the Technology Architecture.
These quality gates include, where applicable:
Implementation Governance ensures that releases cannot be approved until all required validation activities have been successfully completed.
The architecture is expected to evolve throughout the lifetime of the project.
Potential triggers include:
All architectural changes follow the same governance process regardless of their origin.
Implementation Governance defines:
The result is a governance model that protects the long-term architectural integrity of LUNA Charts while enabling collaborative open-source development.
No structural changes were introduced in this document during this iteration.
This governance model is fully aligned with: