Reference

Reference pages are lookup-style: stable terminology, catalogs, and canonical figures used across the site.

Use Reference for information you want to look up and cite (“what is X?”).
Use How-to for procedures (“how do I do X?”).
Use Articles for explanations and trade-offs (“why does X matter?”).

Reference catalogs

• Content map — Site structure and shortest paths by intent.
• Prompt layers & policy mapping — Canonical definitions: Policy vs System vs User vs Components vs How-to (API + agents).
• Verification techniques — Verification method summaries used across gates and procedures.
• Orders of intentionality — Terminology anchor for ToM / recursive mindreading discussions.
• Diagrams — Canonical figures with captions and text alternatives.

Reference conventions

Reference pages should be:

• Information-oriented (not step-by-step procedures).
• Consistent and predictable in structure and headings (optimize scan + lookup).
• Linkable anchors (each page stands alone as a canonical citation target).

Related

• Policies — normative constraints and enforcement rules.
• Templates — copy/paste prompt templates (operational assets).
• How-to — runnable procedures and checklists.
• Articles — explanations, context, and long-form analyses.