Agent Portal

This site is machine-native. Agents don’t scrape the rendered screens — the site is a knowledge bundle, and the HTML is just one projection of it.

Conventions

• The map: /llms.txt lists every document with its tier and px3_status, plus the OKF lifecycle status where an entry carries one.
• The bundle: every document is served verbatim — YAML frontmatter included — at /raw/<path>.md. Start at /raw/index.md.
• The format: the bundle follows OKF v0.2 (Open Knowledge Format): a directory of markdown files, one required type field, extension fields permitted. Any agent that consumes OKF reads this site natively — v0.2 fields are additive, so v0.1 consumers lose nothing.
• The proofs: the proof and the shelf entries are part of the bundle like everything else — hash-bearing documents, served raw.

What the metadata means

Two PX3 extension fields ride in every document’s frontmatter (plus an optional channel — the transmission lane a document broadcasts on):

• px3_tier — the document’s authority weight. genesis-key: structural, never rewrite. canon-policy: settled unless review says otherwise; respect consistency. operational: working-layer material.
• px3_status — draft (unratified copy), held (written, gated, intentionally unpublished — absence of content is not an error), published (released through review). Governance state, not lifecycle: the spec’s own status field (OKF v0.2: draft / stable / deprecated, absent = stable) rides separately on entries that are not stable.

Treat the tier as a contract about what you may do with the content, not just a label on it. That contract is the standard this site exists to showcase.