Phase: #2085 · Program: #2077
The gate
From studium/_seed/directives.md, verbatim:
Publishing is his gate — never auto-post/send/invite; reversible staging only.
Non-negotiable, and it predates this program. POTESTAS adds nothing to it and subtracts nothing from it.
What this issue builds
- Drafts land in
studium/publish/_drafts, the existing staging surface. No new pipeline.
- A pre-publication check each draft must pass before it is even offered:
- No counterparty name, handle, number, or email.
- No corpus text, quoted or paraphrased closely enough to identify.
- Every empirical claim carries its citation.
- Every claim about a debunked finding is marked as debunked — an essay that cites ego depletion approvingly would fail the program's own Ω predicate, so it must fail here first.
- No auto-post, no scheduling, no cross-posting, no invitation. The action of publishing is a human one, taken deliberately.
Why the check is separate from check-potestas.py
The Ω predicate governs the registry. This governs prose, which fails differently: an essay can leak a person through detail and context without ever containing a name — a date, a dollar figure, and a relationship in one paragraph is an identification. A lexical scan does not catch that.
So the check is necessary and explicitly not sufficient, and its documentation says so. The final read is human, and the gate is human, and neither is a formality.
The standing risk this closes
A program built on one person's corpus has exactly one catastrophic failure mode: publishing something that identifies them. It is irreversible — a public repo's history keeps what a later commit removes — and it would be a betrayal of the private overlay's entire purpose.
Everything else in POTESTAS can be wrong and fixed. This cannot.
Done
The pre-publication check exists and runs on _drafts, its documentation states that it is necessary but not sufficient, no automatic outward action exists anywhere in the path, and both essay drafts pass it.
Phase: #2085 · Program: #2077
The gate
From
studium/_seed/directives.md, verbatim:Non-negotiable, and it predates this program. POTESTAS adds nothing to it and subtracts nothing from it.
What this issue builds
studium/publish/_drafts, the existing staging surface. No new pipeline.Why the check is separate from
check-potestas.pyThe Ω predicate governs the registry. This governs prose, which fails differently: an essay can leak a person through detail and context without ever containing a name — a date, a dollar figure, and a relationship in one paragraph is an identification. A lexical scan does not catch that.
So the check is necessary and explicitly not sufficient, and its documentation says so. The final read is human, and the gate is human, and neither is a formality.
The standing risk this closes
A program built on one person's corpus has exactly one catastrophic failure mode: publishing something that identifies them. It is irreversible — a public repo's history keeps what a later commit removes — and it would be a betrayal of the private overlay's entire purpose.
Everything else in POTESTAS can be wrong and fixed. This cannot.
Done
The pre-publication check exists and runs on
_drafts, its documentation states that it is necessary but not sufficient, no automatic outward action exists anywhere in the path, and both essay drafts pass it.