Documentation / Participate
Community and guardianship
Open proposals, guardian approval and publication from main.
Purpose
Anyone can read this repository, open a question, fork it and propose a pull request. Publication into main requires the configured guardian review and passing checks. Repository write access is not required to propose knowledge. Contributor examples must be synthetic or appropriately anonymised.
Initial guardians
Initial guardian: @ismael-lab. Guardian identity is recorded in CODEOWNERS. With one guardian and no bypass, a pull request authored by that same guardian requires another authorised guardian before it can be approved; self-approval is not a substitute for review.
Contribution flow
- Open an issue with the context and proposed improvement.
- Edit the Markdown in a fork or a permitted working branch.
- Keep language editions and diagrams consistent; explain any translation gap.
- Open a pull request with rationale, evidence and limitations.
- The guardian reviews content and required checks; new changes invalidate stale approval.
- A guardian merges the accepted change into protected main.
- The website imports a pinned snapshot of main; the published source revision is displayed with each guide.
Knowledge publication
The website reads a versioned snapshot of the approved main branch, not a contributor branch. Its maintainers run the documented knowledge synchronization and site release. Reading, editing and publishing are separate steps. A contribution appearing in a pull request is not automatically part of the published framework.
Scope and limitations
Original framework text, diagrams and templates: CC BY 4.0. Website code: MIT. KDV marks and third-party references retain their own rights; the licences do not grant trademark rights.
Continue reading
Original KDV Framework knowledge. Working community edition 0.1. CC BY 4.0. References retain their owners’ rights; no official assessment or certification is implied.