# Format Standard
This standard adapts Lore's format canon for agent-spec documentation.
## Markdown
- Use one H1 per page.
- Do not skip heading levels.
- Use fenced code blocks with language tags.
- Use tables only for tabular data, not page layout.
- Use relative links for repository-local documents.
- Use GFM callouts only when the content is a real note, tip, important point,
warning, or caution.
## Artifact Links
- Link implementation requirements with `REQ-*`.
- Link decisions with `ADR-*`.
- Link Task Contracts with their path under `specs/`.
- Prefer explicit source trace entries over prose-only claims.