AI Contributing Guide

This guide is for AI agents working on 0x0 public docs, site, and libraries.

Ground Rules

• Read current 0x0 docs before writing new public claims.
• Prefer implemented 0x0 evidence over current unsupported language wording.
• Use the current embedded/hardware/distributed boundary docs when writing

generic runtime claims; keep target-specific hardware, boot, RTOS, cluster,

and certification claims out of current docs unless the 0x0 repo has matching

implementation evidence.

• Do not run broad compiler or docs gates by default.
• Do not mutate remote static sites without a deployment milestone, dry run,

rollback plan, and smoke checks.

Safe Checks

Use milestone-specific public docs checks:

make public-docs-milestone-4-check
make public-site-link-check
make public-site-build-check

Claim Discipline

Before writing "0x0 supports X", find one of:

• source implementation;
• test or smoke evidence;
• reference doc;
• runtime boundary contract;
• release artifact;
• explicit app-specific acceptance evidence.

If that evidence does not exist, write "planned", "deferred",

"app-specific", "test-adapter-only", or "unsupported".