decisions: ratify Charter v1.3 (Notion-primary cross-shift signals)

decisions/2026-05-18-charter-v1.3-ratification.md

@@ -0,0 +1,62 @@
+# 2026-05-18 — Charter v1.3 Ratification (Notion-primary cross-shift signals)
+
+**Status:** EXECUTED 2026-05-18 SGT
+**Authority:** CEO ratification via Standing Directives entry `CHARTER-v1.3-RATIFIED`
+**Supersedes:** Rockefeller Team Charter v1.2 (2026-05-09) + Constitution v1.2
+**Trigger:** Terminal surfacing on 6th consecutive run — Runs #30 Mon → #35 Sun
+**Notion canonical page:** https://www.notion.so/364017e7fcf281a784bff1a4bf21aa36
+
+## TL;DR
+
+Charter v1.2 mandated Worker tag-query (`recall_by_tag(["rkfl","team-signal","to-scanner"])` / `to-harness`) as the cross-shift teammate-signal channel. The Scanner v3.8 prompt was authored before that update and operated Notion-primary throughout. Six weekday-equivalent runs (#30–#35) passed cleanly under v3.8; the Worker channel returned HTTP 403 in Run #35's Harness intake. v1.3 ratifies the operationally authoritative state: Notion-primary for cross-shift teammate signals; Worker remains canonical for Constitution/Charter body + scored ledgers.
+
+## What changed
+
+### Retired (effective 2026-05-18)
+
+- Charter v1.2 §"The team rituals" bullet 2 (Worker tag-query for cross-shift signals)
+- Charter v1.2 §"How we win" bullet 3 (same)
+- Constitution v1.2 clauses referencing Worker tag-query as the read-required cross-shift channel
+
+### Replaced with
+
+- Cross-shift signals flow via Notion teammate-signal sections at the end of each Scanner brief (→ Harness) and each FEED output (→ Scanner)
+- Worker memory append-only writes encouraged as audit trail, **read-optional, never read-required**
+- If the Notion section is empty/missing, agent proceeds without cross-shift input and logs honesty-contract entry. No fallback to Worker tag-query
+
+### Unchanged
+
+- Trophy: 1+ ORIGINAL EDGE / month sustained
+- Roster: Harness 02:00 SGT / Scanner 04:00 SGT
+- Honesty contract (non-negotiable)
+- F7 Consensus Burn thesis-level
+- Tier matrix + $100 per-ticker cap
+- Worker tag-query READ-REQUIRED for: edge ledger, rejection-ratio, harness-consumption, tier-graduation, active-position
+- Gmail failover for both Worker and Notion write failures (15+ consecutive CLEAN runs precedent)
+
+## Why default-to-ratify, not default-to-reverse
+
+1. v3.8 Notion-primary has operated cleanly for 6 weekday-equivalent runs (#30–#35)
+2. Worker channel is failing in production (HTTP 403 in Run #35 Harness intake; FEED 2026-05-18 fired without absorbing Run #34 calibration — real operational impact, not theoretical)
+3. Reversing asks 4 agents (Builder, Strategist, SPIDER, Hitman) + Scanner to coordinate a mid-week prompt swap with a known-broken channel
+4. The Notion timeout pathology that triggered v1.2 has not recurred during the 7-day v3.8 window — the v1.2 cure may have been worse than the disease
+
+## Implementation checklist
+
+- [x] Add ACTIVE DIRECTIVE bullet to CEO Standing Directives page (2026-05-18 SGT)
+- [x] Create Charter v1.3 Notion page under 🎯 Rockefeller Intelligence — 10000x Scanner parent
+- [x] Commit decision record to `daee-engine/decisions/`
+- [ ] Builder next run: append `rkfl-constitution-v1.3` + `rkfl-charter-v1.3` records to Rockefeller Memory Worker (append-only, v1.2 stays in history)
+- [ ] Builder next run: update Harness v1.4 prompt — remove `recall_by_tag` AWAKEN step, replace with Notion-section parse (~15 min)
+- [ ] Scanner v3.8 prompt: no change required (already operating per v1.3)
+
+## Effective at
+
+Whichever fires first:
+- Scanner Run #36 Mon 2026-05-18 04:00 SGT
+- Harness Run #24 Tue 2026-05-19 02:00 SGT
+
+## Adjacent context
+
+- CTEF-conformance handler shipped same morning: `/.well-known/ctef-conformance` LIVE at `dominion-observatory.sgdata.workers.dev`, HTTP 200, `ctef-conformance-v0.3.2` schema. T-1d before CTEF v0.3.2 publishes 2026-05-19.
+- Standing Directives sync Worker remains separately blocked (bootstrap not shipped); this ratification does not depend on it.