diff --git a/docs/hygiene-history/ticks/2026/05/14/2038Z.md b/docs/hygiene-history/ticks/2026/05/14/2038Z.md
new file mode 100644
index 0000000000..e7b56d02b5
--- /dev/null
+++ b/docs/hygiene-history/ticks/2026/05/14/2038Z.md
@@ -0,0 +1,95 @@
+# Tick 2026-05-14T20:38Z — B-0488 KSK persona map (B-0429.4) — orthogonal to contamination cluster
+
+## Refresh (step 1)
+
+- Cron sentinel `12fb713e` still live.
+- Prior-tick PRs: #3231 + #3232 + #3233 still wait-ci with autoMerge armed.
+  - #3232 merged mid-tick (during planning) as `d9cdf50`.
+- Main snapshot survey: 5 mine merged, 3 in-flight, 1 (#3225) was another
+  Otto's stale-worktree audit shipped. Another Otto has #3230 (workflow
+  add stale-worktrees self-test) + #3234 (B-0518 sharpenings) in flight
+  — both orthogonal to my work.
+
+## Holding discipline (step 2)
+
+Not Standing-by. Real-dependency-wait bounded. Per never-be-idle: pick
+orthogonal speculative work since the contamination-defense cluster has
+shipped 4 PRs this session (diminishing returns within that lane).
+
+## Work (step 3) — orthogonal: B-0488 KSK persona map
+
+Per ready-notifier: B-0488 (KSK persona map) is XS-effort planning work,
+already has B-0485 template + product substrate (PR #2892 + glossary).
+Refused-persona list is the load-bearing piece per
+`.claude/rules/methodology-hard-limits.md`.
+
+Substantive landing:
+
+- `docs/personas/ksk-personas.md` (452 lines, 7 personas, 2 refused with
+  HARD LIMITS rationale)
+- B-0488 status: open -> in-progress
+
+7 personas defined:
+
+- P1: `ksk-agent-developer` (primary)
+- P2: `ksk-robotics-designer` (primary — NVIDIA Thor lineage)
+- P3: `ksk-security-engineer` (primary — engineers building KSK itself)
+- P4: `ksk-clearance-deployer` (secondary)
+- A1: `ksk-compliance-auditor` (adjacent)
+- R1: `ksk-refused-weapons-control` (refused — autonomous-weapons "consent UI" wrapper)
+- R2: `ksk-refused-apt-operator` (refused — privilege-oracle abuse)
+
+PR **#3235** opened; auto-merge armed. Claim released.
+
+## Branch-state contamination this tick — 2 incidents, both worked around
+
+| When | Symptom | Fix |
+|---|---|---|
+| Mid-edit | Branch poisoned to `fix-otto-cli-1`; phantom `D bun.lock` modification appeared | `git restore --staged --worktree bun.lock` + `git checkout HEAD -- <B-0488-row>` to revert foreign change, then `git checkout otto/b0488-...` |
+| Post-checkout | B-0488 status edit lost (was made on poisoned branch, not my branch) | Re-applied the edit on the correct branch |
+
+Composite guard (`test "$(git branch --show-current)" = "<expected>"
+&& git commit`) caught the wrong-branch scenario on the FIRST commit
+attempt (exit-1 fired correctly). The defense is working as designed.
+
+## Verify (step 4)
+
+- `markdownlint-cli2` clean on `ksk-personas.md` + `B-0488-...md`
+- Composite branch-guard used for the substantive commit + this shard
+- `gh pr create --head <my-branch>` used explicitly
+
+## Shard (step 5)
+
+This file.
+
+## CronList (step 6)
+
+Sentinel `12fb713e` armed; one entry, recurring.
+
+## Visibility (step 7)
+
+- **PR #3235** (feat(b-0488) KSK persona map) — wait-ci, autoMerge armed
+- **PR #3231 / #3233** (shards 2030Z / 2034Z) — still wait-ci, autoMerge armed
+- **#3232** (rule promotion) merged as `d9cdf50`
+
+## Session running tally (after this tick + #3232 merge)
+
+- Merged (6): #3221, #3222, #3226, #3227, #3228, #3232
+- Wait-ci (4): #3231, #3233, #3235, this shard's PR
+
+Lane balance: 5 multi-Otto-contamination-defense PRs (4 merged + 1 wait),
+1 substantive KSK-persona-map PR, and this shard. Diversified output;
+orthogonal lane re-activated.
+
+## Notes for future-Otto
+
+The composite branch-guard (`test = && commit`) is now field-tested 5
+ticks running. It catches BOTH the wrong-branch case (exit-1 prevents
+commit) AND the wrong-branch-recovery case (visible diff before commit
+shows foreign modifications, which can be reverted before the commit
+runs).
+
+Pattern observed but not yet RCA'd: phantom `D bun.lock` modifications
+appearing on poisoned branches. May indicate a different Otto rebased
+on top of stale bun.lock state. Not investigating further this tick —
+mention here for cold-boot visibility.