Skip to main content
Public documentation contributions should make BRIK64 easier to understand and safer to use.

​
Useful Contributions

  • Clearer PCD examples.
  • Better monomer explanations.
  • Agent workflow improvements.
  • Glossary corrections.
  • Release and installation evidence.
  • Typo and navigation fixes.
  • Broken link reports.

​
Evidence For Wording Changes

When proposing wording about evidence, certification, platforms, releases or security, include the artifact or release source that supports the wording.

​
Pull Request Checklist

Pages changed:
Reason:
Evidence source:
Commands run:
Screenshots if visual:
Risky terms checked:

​
Public Docs Style

Prefer direct product language:
  • what exists;
  • how to use it;
  • what evidence is produced;
  • what the user should inspect next.
Avoid internal policy phrasing in public docs.