Cult OS Exposure Engine — category seeding (2026-08-10)
Move 3 of the deep-positioning action plan: “closure-ready” and the 15 laws entered the automated surfaces branch staff touch daily. All surfaces were pre-approved for doctrine in the Cult OS Blueprint (Layer 2, “no audiences excluded”); wording used verbatim from the approved blueprint.
Surfaces live
| Surface | What changed | Where |
|---|---|---|
| Cert delivery email | Body now says “closure-ready certification package”; muted footer below signature: “This certificate lives permanently at unlikely.report. It will outlive this email, the sale of the house, and everyone’s inbox.” | routes/cert.py _build_cert_body (entirely-api 2cd4baa) |
| Morning branch SMS | Mondays only: one law appended after the schedule numbers. ISO-week rotation so consecutive Mondays walk the list. First seasoned send: Mon 2026-08-17 (law 5, “Handled means you never think about it again.”). | services/branch_schedule_preview.py |
| Portal login | Law of the day under the sign-in card, serif italic, understated | portal-v2 Login.tsx (03079e7) |
| Portal sidebar | Same law, small and faint, above the sidebar footer on every page | portal-v2 Sidebar.tsx |
| Cert preview panel | Toolbar label: “Closure-Ready Certification Package” | portal-v2 CertPreviewPanel.tsx |
Mechanics
services/doctrine.py(entirely-api) andsrc/data/doctrine.ts(portal-v2) carry the same approved law wording — change both or neither.- Rotation is deterministic (day-of-year / ISO-week modulo 15): same law for every user on a given day, stable across retries. No randomness.
- The dispatch cron shipped 2026-08-11 (see monthly-dispatch-drafter); its sign-off slot pulls from services/doctrine.py so the wording stays single-source.
Not done deliberately
- Orientation Card print run (30-day item 2) — physical artifact.
Connections
- seeds doctrine into: cert-generator-v3