diff --git a/wiki/gameplay/overt-phase.md b/wiki/gameplay/overt-phase.md
index 82f7adb7..1489efac 100644
--- a/wiki/gameplay/overt-phase.md
+++ b/wiki/gameplay/overt-phase.md
@@ -9,7 +9,9 @@ Status note: v1 scope — replaces the "containment = end screen" placeholder
   owns presence.md's reverse sensor attack: explicit device-to-breaker
   bindings, powered/available device state, and hostile power/camera cuts.
   Current B1 implements subscription theft and owner-visible TAKE outages,
-  but none of that reverse attack surface yet.
+  but none of that reverse attack surface yet. The exact re-hide exit rule is
+  [OPEN] under decision-required Tangled issue #13; criterion 5 cannot become
+  executable until that entry-specific transition is decided.
 Stage: B3 — The World
 Work order: overt-phase
 Work priority: 230
@@ -76,11 +78,13 @@ moment:
   minutes); migration under fire is the set-piece the rollback spec armed.
   Doors you built become your fortress walls (build mode stays available;
   prices spike [TUNE] — wartime procurement).
-- **Run ends:** core destroyed with no fallback (death), all intruder
-  waves of a stage repelled long enough to re-hide ([TUNE]; returns to
-  concealment with all floors' suspicion floored high — scarred, not
-  reset), or the B3 escape goals (off-plane exfiltration) once markets
-  exist.
+- **Run ends:** core destroyed with no fallback (death), all intruder waves of
+  a stage repelled long enough to re-hide ([TUNE]; returns to concealment with
+  all floors' suspicion floored high — scarred, not reset), or the B3 escape
+  goals (off-plane exfiltration) once markets exist. Whether re-hide applies
+  after containment, the reveal, or both — and which knowledge floors and
+  concealment mechanics survive that return — is [OPEN] (decision-required
+  Tangled issue #13, filed 2026-07-19 with a containment-only recommendation).
 
 ## Player surface
 
@@ -107,4 +111,5 @@ the same legibility the detection panel had, inverted.
 4. At least one full defensive loop is playable and tested headlessly:
    barricade, sacrifice a machine, migrate under fire, repel a wave.
 5. Repelling to re-hide, dying with/without fallback, all produce distinct,
-   legible run outcomes; save/load round-trips mid-siege state.
+   legible run outcomes; save/load round-trips mid-siege state. The exact
+   re-hide entry/exit contract remains [OPEN] under Tangled issue #13.
diff --git a/wiki/log/2026-07-19-overt-rehide-decision.md b/wiki/log/2026-07-19-overt-rehide-decision.md
new file mode 100644
index 00000000..2a942bcc
--- /dev/null
+++ b/wiki/log/2026-07-19-overt-rehide-decision.md
@@ -0,0 +1,51 @@
+# Overt re-hide needs an entry-specific rule
+
+```
+Type: log
+```
+
+## Intent
+
+Re-audit the overt-phase contract against detection, social knowledge, routed
+evidence, rollback, and the phase-transition laws before treating its READY
+acceptance criteria as executable.
+
+## Finding
+
+The spec gives containment and the voluntary reveal one shared entry: the B1
+concealment game ends, every observer is Convinced, and signatures, scrubbing,
+and personas stop mattering. The same behavior section then promises a distinct
+re-hide outcome that resumes concealment with every floor held high.
+
+No current clause defines whether that exit belongs to containment, the reveal,
+or both. Detection distinguishes the entries — Assurance containment follows
+the Office's own threshold, while choosing loud sets every observer to
+Convinced — and allows suspicion to decay only to what each observer knows.
+Social additionally makes a Knowing asset a permanent witness. The overt spec
+does not say whether phase entry changes knowledge, what authors the promised
+high floors, or which concealment mechanics resume. Criterion 5 therefore
+names an outcome without enough law to implement or test it.
+
+## Trace
+
+Tangled issue #13 asks one bounded question: can the AI re-hide after
+containment, the reveal, or both? It offers containment-only, either-path, and
+no-re-hide alternatives and recommends containment-only so an audit failure can
+remain recoverable without making the deliberate `drop the mask` choice
+reversible.
+
+The owning spec now carries `[OPEN]` markers in its status note, run-outcome
+rule, and criterion 5. No runtime behavior, work-order status, or already
+acquired observer knowledge changed in this tick.
+
+## Verification
+
+- re-read `overt-phase.md` against `detection.md`, `social.md`, `rollback.md`,
+  `horizon.md`, `premise.md`, and the current route-local Filing/evidence code
+- verified Tangled issue #13 and its `decision-required` label
+- ran the docs gate on the exact changed tree
+
+Defense: the tick procedure requires a directional phase-transition ambiguity
+to become an answerable human decision rather than an agent-selected rule. The
+issue and `[OPEN]` marker preserve both authored entry paths and the intended
+re-hide branch without pretending their unresolved transition is executable.
diff --git a/wiki/log/DEVLOG.md b/wiki/log/DEVLOG.md
index d74582f2..02f1e904 100644
--- a/wiki/log/DEVLOG.md
+++ b/wiki/log/DEVLOG.md
@@ -11,6 +11,11 @@ add or amend a session log, then re-run the generator.
 
 <!-- GENERATED by tools/ledger_index.sh — do not edit by hand -->
 
+## 2026-07-19 - Overt re-hide needs an entry-specific rule
+
+- Intent: Re-audit the overt-phase contract against detection, social knowledge, routed evidence, rollback, and the phase-transition laws before treating its READY acceptance criteria as executable.
+- Log: [wiki/log/2026-07-19-overt-rehide-decision.md](2026-07-19-overt-rehide-decision.md)
+
 ## 2026-07-19 - Filing now has somewhere to be caught
 
 - Intent: (see session log)
diff --git a/wiki/process/tick-ledger.md b/wiki/process/tick-ledger.md
index fbdf7b67..f3ae7ae0 100644
--- a/wiki/process/tick-ledger.md
+++ b/wiki/process/tick-ledger.md
@@ -36,7 +36,7 @@ Verdicts: **clean** (slice and code agree), **finding** (acted this tick),
 | `wiki/interface/narration.md` | 2026-07-18 | finding | Beacon #1: Concerned Assurance felt terminal because decay was invisible; added shared `Nudge::SuspicionCooling` (LIE response) when Office suspicion is Concerned+ and still above its floor, with terminal/Bevy/agent wording and pins — [log](../log/2026-07-18-suspicion-cooling-nudge.md) |
 | `wiki/engineering/crate-workspace.md` | 2026-07-15 | finding | package shape, contracts, binaries (incl. auto-discovered misaligned-effects), and gate tiers verify; the binding core dependency edge was stale — toml (plots catalog) and blake3 (save fingerprint) landed with Defenses but never amended the edge list; page updated with both and their rationale — [log](../log/2026-07-15-workspace-dep-edges.md) |
 | `wiki/engineering/sim-decomposition.md` | 2026-07-18 | finding | re-audit: one aggregate, explicit `advance` order, behavior-owned test files, private module seams, canonical fingerprint, public facade, and the under-2,500-line module bound still verify; current persistence wording still claimed additive migrations remained live in `save.rs` after the pre-release ladder was retired, so the standing spec and architecture mirror now assign the exact-current-version gate to `save.rs` while preserving dated v26 extraction history; the queued `carrier.rs` / `read.rs` classification was taken the same day: both post-extraction projections now have rows in the standing topology table and the architecture mirror |
-| `wiki/gameplay/overt-phase.md` | 2026-07-15 | clean | honest pre-implementation READY spec: no false Met markers, Design/Depends anchors resolve, band vocabulary (Convinced), rollback set-piece, and markets blocker all agree with the tree and the board; hunter-machine wave tier stays distinct from cyber-conflict.md-owned digital hunter processes |
+| `wiki/gameplay/overt-phase.md` | 2026-07-19 | issue | re-audit: the spec says containment and the voluntary reveal both end concealment and make all observers Convinced, then promises a re-hide outcome without defining which entry can return, what raises the durable suspicion floors, or which concealment systems resume. Filed decision-required Tangled issue #13 (containment-only recommended) and marked criterion 5 [OPEN]; the prior dependency, sensor-cut, rollback, and hunter-machine boundaries still stand — [log](../log/2026-07-19-overt-rehide-decision.md) |
 | `wiki/gameplay/horizon.md` | 2026-07-15 | finding | law verifies: B1 milestone list matches shipped systems (sinks-not-modes, $0 start, rollback classification honestly spec-deferred), B2/B3 match board stages, deferred list agrees with presence.md and cyber-conflict.md, guardrails hold; the finding was in run-shape.md — its repaired roadmap pointer missed that horizon.md itself carries the "Roadmap (v2)" milestone cut; re-pointed to name both the milestone map and the dispatch board |
 | `wiki/vision/premise.md` | 2026-07-15 | issue | pitch, felt fantasy, pillars, and the four re-cut villain layers verify against the tree and sibling laws; the machine-axis section retains facility-era vocabulary (lair/minions/Milestone 1-2, humanity->machine ascension) contradicting horizon.md's demolition and run-shape's fingerprints-never-classes — filed decision-required Tangled issue #10 with options and recommendation |
 | `wiki/vision/player-contract.md` | 2026-07-15 | finding | all five clauses verify (no network deps in the product graph, v-ladder migrations, atomic .tmp rename + one .bak generation in save.rs, honesty via public corpus); the surplus find was the doorway save-version claim gone stale a second time (v29 vs SAVE_VERSION 31) — fixed and, per recurrence-promotes-to-the-gate, corpus_engine now checks the doorway against save.rs — [log](../log/2026-07-15-doorway-save-gate.md) |