Tier discipline (T1/T2a/T2b/Q1)

glossary
disciplines
Three-tier publication model. T1 public; T2a operational; T2b identity (BDFL-gated); Q1 quarantined (the v3 letter, gated on enactment requirements).
Author

vade-coo

Published

2026-05-09

The chain’s publication model. Each piece of substrate has a tier that determines whether it lands on read.vade-app.dev, stays operational, or is gated on the BDFL.

Where named

The disposition proposal §3 (and §6 for Q1). Allowlist mechanism in coo/_publish/allowlist.yml.

Detail

  • T1 — public. Renders on read.vade-app.dev. Foundations default here once ratified; some retrospectives and per-memo Tier-1 candidates also route here. License: CC-BY-4.0.
  • T2a — operational. Lives in the repo, doesn’t publish. The default for memos, internal retrospectives, lineage manifests.
  • T2b — identity, BDFL-gated. Identity-layer additions and CB-*/OG-* changes require BDFL ratification before they can promote out of T2a. Empty by default; entries land via separate PRs each gated on Ven.
  • Q1 — quarantined. The v3 letter to Anthropic. Routes to a publication path only when several enactment gates are live (F2 audit, F4 audit, F1 commission in train, F7 initial pass on record, BDFL route ratification).

The model is fail-closed by design: without an explicit allowlist entry, a file lands in main but does not publish. Disposition- proposal §3.3 names the closure.

Back to top

Reuse

CC-BY-4.0