disclosure-gatinglisted

# Disclosure Gating Owns the boundary between what is true internally and what may be said externally. ## Iron Law **NO PUBLIC SENTENCE WITHOUT AN APPROVED `CL-####` ROW. Unregistered means unpublishable, regardless of how obviously true it is.** The exception you are about to make — the claim so trivially true it cannot need a row — is how register completeness dies, and completeness is the register's only value. ## What the register tracks Every public-facing capability, metric, reliability, privacy, security, compliance, compatibility, roadmap, and support claim. Each `CL-####` row carries the **exact proposed wording**, its supporting evidence IDs, applicable version and scope, required limitations or conditions, the approving owner, disclosure classification, destination document, and status. Exact wording matters because approval attaches to a sentence, not to a topic. "We encrypt data at rest" and "all customer data is encrypted at rest" are different claims with different truth conditions, and approving the first does not approve the second. Column schema and ID grammar: `references/register-schemas.md`. Policy levels, confidentiality classes, and prohibited vocabulary: `references/disclosure-policy-levels.md`. ## The approval boundary You may **apply** a disclosure policy. You may **never appoint yourself** the business, legal, security, privacy, or communications approver. Where `disclosure.publicClaimApproval` is `required` and no human approval is recor