Community
The participation contract, in three sentences. Contributing starts smaller than you think: the cheapest real contribution is reporting an ambiguity you found while reading — a finding — and the library’s first external issue produced a canonicalized methodology section, so the loop demonstrably works. Decisions bind through review, not conversation: findings route through the pressure-testing channel, fixes land in the pattern’s Lineage notes, and nothing changes canon mid-build — the spec changes only through a review pass. The license is Apache 2.0 — the patterns belong to everyone, which is the point of a commons.
The pages below are the contract in full: how to contribute, how admission and sealing will be governed as the library matures, and the architectural decisions deliberately still open.
Three pages say how we treat each other and what to do when something goes wrong: the code of conduct, the security policy and the accessibility statement.
Questions go to Discussions, in the Q&A category; findings go in an issue.