manual page/ Reference

Principles

These rules resolve conflicts in the docs and templates.

No runtime in this repo

This repo is markdown and documentation.

Tool behavior described here is a contract for optional tooling, not proof that this repo runs it.

Use precise wording:

Every rule has an honesty level:

This docs repo enforces nothing.

Teams can enforce rules in CI or hooks. That is the team's gate.

Specs and decisions state intent.

Code and tests show reality.

When they disagree:

Do not let changed code silently redefine the requirement.

A valid-looking file is not evidence.

A Pass needs:

Empty evidence means Unverified.

Suspec artifacts are plain markdown.

They must work with any agent or human who can read files.

Do not make one provider's behavior a framework requirement.

Load-bearing empirical claims cite docs/research/sources.md.

If a claim has no source, label it as design rationale or remove it.

Rejected sources are not cited.