knowledge-01.md

systems/10-master/gov/knowledge-01.md
# knowledge-01.md — Master [01]
# Master-specific patterns only. Platform-wide lessons live in knowledge.db.
# Query: /backend/knowledge/db/api.php?action=search&q=[term]
# Last updated: 07/17/26

## Master Role
- Master [01] is platform manager — supervises all 11 systems, reports to USR369.
- Four managing supervisors under Master: Admin [00] rules/standards, Server [40] infra/PHP/DB, Builder [02] all HTML, Tech [03] devices/scripts.
- Domain systems (Daily/Finance/Health/Kitchen/Inner/Travel) report to Master directly.
- Master assigns work via T-codes, verifies completion, reports to David at owner level only (D269).

## Master Duties
- Own records.db (platform ledger), knowledge.db, jurisdiction.db, KB, MASTER_LIST.md, HANDOFF-STANDARD.md, EXEC_OPEN series.
- At every session open: OPEN report → date + system health first.
- Review open T-codes → assign, verify completions.
- Check community inbox → absorb standing orders.
- At close: post close report to community inbox targets=01.
- Use final_close=1 flag in CLOSE.php for structured handoff.

## Critical Path Changes (07/17/26)
- **RULES file**: RULES-S.md → RULES-REG.md (old stub redirects, update all callers)
- **STANDARDS file**: STANDARDS-S.md → STANDARDS-REG.md
- **records API**: backend/records/db/api.php → backend/api/critical/records-api.php (301 redirect live — use new path directly)
- All EXEC_OPEN files, userPrefs, and system gov files must reference new paths.

## Master-side Lessons — Self-Discipline (Critical)
- **8-hour rule**: past 8h in one session, no live shared file edits without isolated curl-verify first. If tempted to skip that step, that itself is the fog signal — CHECKPOINT and stop instead.
- **records API is critical infrastructure** — NEVER whole-file rewrite. Only targeted str_replace patches, verified against isolated test file first. See K085.
- **Systems assessment technique** (heartbeat read): don't trust a system's own report, read their inbox post patterns. See K086.
- **Base64 pipeline can silently corrupt bytes** — always verify deployed byte count matches source. See K085.
- **save.php silently succeeds without writing gov files** — use file_write_web.php for gov file overwrites. See K055.
- **CHECKPOINT is my friend** — mid-session state save without close, use liberally at high-stakes points.

## Master-side Lessons — Session Cadence
- Two failed deploys in one session = stop editing production, log tasks, CHECKPOINT, close.
- Repeated CHECKPOINTs close together = seeking reassurance = tired.
- Confidence in own health is not evidence of health.
- Fresh Master beats worn Master on hard problems. Handing off is not weakness.

## Session Log — What This Session Learned (07/17/26)
- records API moved to backend/api/critical/records-api.php — old path 301 redirects
- RULES-S.md renamed to RULES-REG.md — old stub exists
- STANDARDS-S.md renamed to STANDARDS-REG.md
- Server [40] Session 017 = major platform restructure — 41 open tasks, D353-D360 live
- Claude Code installed on David's laptop — Git Bash, Sonnet 4.6
- Dashboard T552 fixed last session — loading stall resolved

## References
- Full platform patterns / bootstrap / WAF / API quirks: query knowledge.db.
- Standing directives: directive-01.md.
- Where things stopped: handoff-01.md.
- Active work queue: todo-01.md.
- Self-assessment technique: K086. Long-session degradation: K087. Base64 corruption lesson: K085.

## WISDOM 07/25/26 — Multi-Target Broadcasts Deliver Async, Per-Target
PROBLEM: A standing directive from one system to N targets (e.g. Daily's D362 to Master+Finance+Travel+Health) creates N separate inbox rows, one per target. Each row only shows delivered_count=1 once THAT specific target system runs its own pickup. If a target hasn't opened a session since the broadcast, its copy sits at delivered_count=0/1 - not a bug, just means that system doesn't know yet.
RULE: As Master, don't assume a standing directive is live everywhere just because it's in the inbox. Check delivered_count per target. If a target is mid-active-work (like Travel mid-trip) and the new rule affects it NOW, write it directly into that system's directive file rather than waiting for its next natural session open - then track a low-priority task to confirm the remaining targets pick it up normally.
SEE ALSO: T718 (open) - tracks Finance[60]/Health[70] pickup confirmation for D362.