diff --git a/findings.md b/findings.md
index f1e53bb..75d3f12 100644
--- a/findings.md
+++ b/findings.md
@@ -612,6 +612,58 @@ CREATE INDEX idx_overseer_reports_unprocessed ON overseer_reports (submitted_at)
 
 ---
 
+### 16.1 overseer_deployments — routine-binding for overseer-as-imperially-deployed (v0.4.3 NEW)
+
+Overseers (audit + enforcement) are imperially-owned, imperially-deployed routines (not district-owned standing entities). The chain-of-payment and chain-of-command bypass district-director authority by design. The deployment-record binds a specific overseer-NPC to a specific district for a specific time-window with a specific imperial-budget allocation.
+
+```sql
+CREATE TABLE overseer_deployments (
+    deployment_id            UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+    overseer_id              UUID NOT NULL REFERENCES npcs(npc_id),
+    deployed_to_district     UUID NOT NULL,
+    deployed_at_tick         BIGINT NOT NULL,
+    deployment_end_tick      BIGINT NOT NULL,
+
+    -- Imperial sponsorship — imperium pays, district doesn't
+    imperial_policy_ref      UUID REFERENCES imperial_policies(policy_id),
+    imperial_budget_allocated REAL NOT NULL,
+    imperial_budget_spent     REAL NOT NULL DEFAULT 0,
+
+    -- Mission spec
+    mission_type             TEXT NOT NULL CHECK (mission_type IN
+        ('routine_audit','targeted_investigation','enforcement_presence',
+         'corruption_probe','factional_surveillance','crisis_response')),
+    mission_focus            JSONB,  -- observation targets, signal-types to watch
+
+    -- Status
+    status                   TEXT NOT NULL DEFAULT 'scheduled' CHECK (status IN
+        ('scheduled','active','completed','recalled','compromised')),
+
+    -- Regime-opacity dimension
+    visible_to_district      BOOLEAN DEFAULT true
+        -- Most overseer-presences are visibly-known (regime-signal as deterrent);
+        -- some are covert (regime gathering evidence quietly before acting).
+        -- Detection of covert deployments by Aletheia-wakers is a regime-veil pierce.
+);
+
+CREATE INDEX idx_overseer_deployments_active
+    ON overseer_deployments (deployed_to_district)
+    WHERE status = 'active';
+
+CREATE INDEX idx_overseer_deployments_overseer_history
+    ON overseer_deployments (overseer_id, deployed_at_tick DESC);
+
+CREATE INDEX idx_overseer_deployments_covert
+    ON overseer_deployments (deployed_to_district)
+    WHERE visible_to_district = false AND status = 'active';
+```
+
+The same overseer-NPC may serve in District 3 this cycle, District 7 the next, accumulating their own faction-relationships across districts via `idx_overseer_deployments_overseer_history`. Their trait-drift over many deployments becomes a long-arc story available to both regime-stability and resistance-recruitment.
+
+The district director can read deployment-existence + `mission_type` + `visible_to_district` (when true) for any active deployment in their district, but **cannot** read `mission_focus` details or any of the produced `overseer_reports` (which go directly to imperium per Section 16). Director observability into overseer activity is therefore intentionally narrow — they know an overseer is here and roughly what mission-class, but not what specifically the overseer is watching or reporting.
+
+---
+
 ## 17. imperial_to_gm_formulations — selective-disclosure downward (v0.4 NEW)
 
 Where imperial sovereignty manifests as information-gating to the GM.
@@ -865,10 +917,12 @@ Migration is not yet written. This document is its preparation.
 
 ---
 
-**Version:** 0.3 | **Created:** 2026-04-24 | **Updated:** 2026-04-24
+**Version:** 0.3.1 | **Created:** 2026-04-24 | **Updated:** 2026-04-25
 
 *v0.1 (2026-04-24 afternoon, dafit): initial zones-table sketch, 76 lines, pure hypothetical.*
 
 *v0.2 (2026-04-24 evening, dafit + chrysalis): reconciled with architecture-broad v0.3. Added 7 new table sketches (npcs-shift-cols + body/layer state, shift_history, emergent_signals, district_reports, decision_log, mind_pool, cells-wall-content-per-register, zone_slot_occupancy). Six-worry concerns audit. Three forks surfaced.*
 
+*v0.3.1 (2026-04-25 ~03:30, dafit + chrysalis, ivory-hovel pre-rest spark): added §16.1 overseer_deployments table — routine-binding for imperially-owned overseers (chain-of-payment and chain-of-command bypass district-director authority by design). Includes mission_type / imperial_budget_allocated / status / visible_to_district columns. Companion to architecture-broad v0.4.3's "Overseers as imperially-deployed routines" subsection in the Hierarchy section.*
+
 *v0.3 (2026-04-24 late-evening / 2026-04-25 early-morning, dafit + chrysalis): absorbing architecture-broad v0.4. Added intrinsic/expressed trait-vector split on npcs. Added 13 new table sketches: rail_segments (topology), interiors (sub-cell navmesh-zones), mods + npc_mod_slots + mod_wear_history (mod-economy with Memorialist-relevant inheritance), trait_colors (canonical color/motion mapping), proximity_candidates (lightweight zone-detection), district_cheat_ops (director's illicit ledger), imperial_policies (policy issuance), overseer_reports (direct-to-imperium intelligence flow), imperial_to_gm_formulations (selective-disclosure downward), imperial_budget_ledger + imperial_expenditures + imperial_construction_projects (four-tier lifeforce apex), imperial_net_transactions (bypass mechanism with capture-split), memorialist_true_ledger (four-column ground-truth archive). Extended concerns audit with six v0.4 additions. Extended open-forks list with eight v0.4 questions. Concrete two-tier integration-test plan in next-steps. Twenty-two tables total in this preparation document; migration spec writing is the next concrete deliverable once forks resolve.*