Documentation contribution
Contribution rules
Section titled “Contribution rules”- Inspect the owning implementation, configuration, and relevant tests or manual evidence first.
- Update a product fact when a public capability, compatibility boundary, model, format, data flow, or roadmap status changes.
- Record unresolved hardware, release, provider, privacy, or security claims in
CONTENT_VALIDATION_BACKLOG.mdinstead of publishing assumptions. - Keep Local Mode distinct from remote-provider behavior.
- Do not introduce release dates, compatibility claims, compliance language, or placeholder contacts without approved evidence.
Validate changes
Section titled “Validate changes”cd docs-sitenpm run facts:checknpm run checknpm run buildReview internal links, frontmatter, generated product-fact tables, and the final diff. Run application checks only when the work package changes application code or a documented validation boundary requires it.

