Skip to content

Documentation contribution

  1. Inspect the owning implementation, configuration, and relevant tests or manual evidence first.
  2. Update a product fact when a public capability, compatibility boundary, model, format, data flow, or roadmap status changes.
  3. Record unresolved hardware, release, provider, privacy, or security claims in CONTENT_VALIDATION_BACKLOG.md instead of publishing assumptions.
  4. Keep Local Mode distinct from remote-provider behavior.
  5. Do not introduce release dates, compatibility claims, compliance language, or placeholder contacts without approved evidence.
Terminal window
cd docs-site
npm run facts:check
npm run check
npm run build

Review 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.