Agent Task Workflows

This page defines session-safe workflows for AI or human agents changing 0x0.

Documentation-Only Change

1. Read the target docs and linked reference pages.

2. Update beginner docs and exact reference docs together when behavior is

involved.

3. Run make documentation-impact-check.

4. Run the smallest public-docs gate named by the changed page.

5. Commit only the intended docs and ADR/RFC records.

1. Find the source owner.

2. Add or update the smallest executable test.

3. Update syntax, API, CLI, compiler, runtime, standard-library, and behavior

docs affected by the change.

4. Add an ADR and RFC with a documentation impact review.

5. Run the bounded feature gate first.

6. Run heavy gates only when the task explicitly allows them.

1. Update package metadata and registry evidence.

2. Update package docs, registry docs, and public library pages.

3. Run package or registry gates.

4. Record rollback and provenance evidence.

Use narrow gates while iterating. Leave self-host, release verification,

remote deployment, physical hardware, and broad ecosystem gates to explicit

release steps or commit hooks.

Every implementation, syntax, API, CLI, compiler, runtime, standard-library, or

behavior change must include a documentation impact review. The review must

list updated docs or explain why no documentation changed.