ADR-0012: Publish everything
Status: Accepted Date: 2026-05-19
Context
The vault publishes to Cloudflare Pages — public by default. Need to decide whether any notes should be filtered out of publication.
Decision
Publish everything. No publish: frontmatter, no /private/ folder, no per-type opt-in/opt-out filter. Quartz default config builds the entire vault.
User’s reasoning: most readers won’t visit; published content is reorganization of already-public sources; the value of an honest open notebook outweighs the small risk.
Alternatives considered
- Per-type defaults (e.g.
experienceandsermonsopt-in, rest opt-out): rejected — user explicitly chose not to overthink it. - Default opt-in (whitelist): rejected — too much friction for a system intended to grow fast.
- Audience tiers (trusted-only with auth): rejected — adds infra complexity; public is fine.
Consequences
- (+) Zero filter logic to maintain
- (+) Quartz config stays default
- (+) Honest wrestling visible to anyone studying UC; can help others working through the same questions
- (−) Out-of-context quoting risk (experiential atomics naming non-public individuals): mitigated by case-by-case judgment during batch review — author can anonymize or move to
/staging/-trash before commit - (−) Reversal cost is real (once Google indexes, hard to retract) — accepted by the user
Soft hygiene (not a system, just guidance)
- Experiential atomics naming living non-public individuals by full name → consider first-name-only or anonymizing during batch review. AI may flag, user decides.