Content Metadata
How to read adoption (A) and epistemic tier (T) tags — and how to use Page tools
Some passages on this site carry bracket tags — short codes in square brackets that say how firmly I stand behind the prose and, separately, how strongly a claim is supported. Two letters, two jobs; do not mix them.
You will see them inline, for example [A3 — open mapping] or [T12]. Each tag links back here (or should).
Full tier ladder: The Epistemic Ladder.
Page tools
On most articles, patterns, reference entries, and about pages you will find Page tools — a collapsible panel for reading aids and publication facts.
The panel has two sections, separated by a divider:
Epistemic tiers (inside Page tools)
Show epistemic tiers turns on coloured outlines around passages the author classified with tier markers in source. Hover an outlined block to see its tier name (for example T7 — Hypothesis).
- Page default — when shown, the entry’s overall default tier from frontmatter (not every paragraph has its own marker).
- Tiers assigned by AI — this feature is experimental. On many pages, tier regions were assigned automatically and may contain errors; for now they mainly illustrate how tier highlighting would work, not certify every passage.
- What do tiers mean? — links here and to the full ladder.
If a page has no tier regions, the toggle may have little visible effect. Bracket tags like [T12] in prose work independently of the toggle — they always link here.
Publication (inside Page tools)
Shows when this page entered the public corpus, which release batch it belongs to, and this page’s version number. Committed pages are frozen; if something needs correction, a new version is published and the old one remains readable from Release history.
The publish date also appears in the header byline (next to the site name), directly under the subtitle or title — so you do not need to open Page tools to see when the page was released.
Adoption (A)
Adoption is metadata about my content — whether a passage is settled site doctrine, a working draft, or exploratory material I have not adopted.
The words after the em dash (open mapping, open question, stance not adopted, …) are a short label for that passage — optional, but helps scanning.
Example: A3 — open mapping on the knowledge synthesis term means the L0≈data / L1≈information rhyme is intentional but not yet adopted doctrine — it will be developed in the Synthesizing Knowledge series.
Corpus stance (prose, not brackets)
Many term pages end with a Corpus stance line instead of bracket tags:
External works
Works use frontmatter corpusStance — how this site relates to their work (adopt, partial, context, reject-position). That is parallel to A, but scoped to attribution, not my own passages.
Epistemic tier (T)
T is reserved for the epistemic ladder only — tiers 0–13. It classifies how strongly something is supported (or what kind of record it is at the bottom), not whether I have adopted a passage as site doctrine.
The ladder has two layers: substrate (what was captured) and claims (what we infer or assert above it).
Substrate — tiers 0 and 1
Everything from tier 2 upward is a claim about the Real or about tier-one captures — ranked by support.
Claims — tiers 2–13
These are the rungs you will most often see on assertions and interpretations (full table in The Epistemic Ladder):
Both codes together
Open threads often need both adoption and tier:
Consciousness remains unresolved under non-reductive physicalism. A3 — stance not adopted T12
- A3 — I have not adopted a settled stance on consciousness here.
- T12 — the question itself is an open question on the epistemic ladder (not a failure to tag — a first-class level).
Related
- L–U shorthand —
Lx-U-ynotation (atomicity × uncertainty); popover-friendly summary of the classification grid - Every Statement Has a Tier — why tier discipline matters
- The Epistemic Ladder — full tier 0–13 definitions
- Release history — releases, versions, and immutability
- Philosophical stance — first-person metaphysics; separate from A/T tagging
Authoring reference (repo): content-metadata.md