Boundaries and licensing
Summary
The contract the site runs under. Content is CC BY 4.0 throughout; quoted code and the in-repository methodology guides are Apache-2.0 and keep their notices, with the instruction to keep the repository canonical and generate rather than copy. The do-not-publish list is specific rather than gestural: none of the estate's own financial figures in any form, a review naming a private individual, a security review classified as an attack roadmap for live code, live hostnames and account identifiers, and the villagers brief's market statistics, which that brief itself flags as loosely attributed. The network-boundaries section restates the owns-and-links split with one rule above the table.
Key concepts
- What is deliberately not published
- Licensing
- The deconfliction contract
- The budget boundary in practice
Key ideas
- When a sibling pack has measured something, link the measurement; never re-measure and never paraphrase the number.
- The budget discipline is publishable; the figures around it are not, anywhere.
- The second-source-of-truth rule applies to methodology guides exactly as it does to API references.
- House style: every discipline page ends with its counter-evidence, and the eight-NFR list is quoted verbatim wherever the scope is stated.
On this site
Applied. The do-not-publish list is restated on the shipped page so a reader meets it without having to open the sources.