docs(roadmap): close Lane 5 (killer-app accepted) + refresh stale Lane 1 close-out annotation

Two loose-end doc-sweeps surfaced during a repo health survey:

1. Lane 5 (Tutorial / pedagogy) — close via the killer-app branch.

   `roadmap.adoc` §Lane 5's unblocking condition has two branches: either
   Lane 1 closes, or "a single killer-application example emerges that
   justifies a tutorial track on its own merit". The second branch fired
   2026-05-26: `tutorial/region_exit_audit/RegionExitAudit.agda` is the
   ephapax-L3-corroborated certified region-exit audit example, and
   already carried the in-place self-description as the killer-app
   candidate. The three walkthroughs (region-exit audit / epistemic
   erasure / provenance debugging) all landed in May, build under
   `--safe --without-K` with zero postulates via `tutorial/All.agda`,
   and carry per-walkthrough Smoke pins + honest-bound + matched-negative
   `NotProved-*` ⊤-aliases discipline.

   Edits:
   * `roadmap.adoc` — remove Lane 5 from active lanes, add a Lane 5
     entry under §"Closed lanes" with the close-out route, closing
     artefacts, and retraction-watch carried over. The "Why this counts
     as a kill, not a deferral" subsection makes the second-branch
     unparking case explicit so future audits don't reopen the lane on
     "but Lane 1 isn't closed yet" grounds.
   * `tutorial/README.adoc` — flip the [PARKED] status to CLOSED in the
     section heading + IMPORTANT block; convert the "Killer-app close-out
     check" subsection from a candidacy framing to an ACCEPTED record.
   * `docs/echo-types/MAP.adoc` — update the two Lane 5 / killer-app
     pointers (Walkthrough 1 bullet, track-level docs note) to point at
     §"Closed lanes" instead of §"Lane 5 [PARKED]".

2. Lane 1 — refresh the stale close-out criterion.

   The Lane 1 §"Close-out criterion (falsifiable)" had `[EXPAND]` tag 2
   (related-work pass — Granule / QTT, Uustalu–Vene comonads, coeffects,
   choreographic types, lens/optic vs witness-transport leg) listed
   without a LANDED marker, even though the paper itself records that
   tag 2 was cleared 2026-05-26 via PR #120 (see `paper.adoc:1183` —
   "Related-work [EXPAND] cleared 2026-05-26"). Sections §"HoTT homotopy
   fibres", §"Graded comonads, coeffects, and QTT", §"Lenses and optics
   (the witness-transport leg)" + the 2-categorical rule-out
   (`decisions/no-2-cat.adoc`) are live in the paper; the
   `comparators.adoc` single-page companion table ships the
   axis-by-axis summary.

   Edits to Lane 1:
   * Mark item 1 as LANDED 2026-05-26 with cross-references to the
     three landed paper sections + the cleared tags (1 via PR #73,
     3 via PR #84). Tag 4 (ordinal consumer-evidence appendix) is
     explicitly flagged as gated on Lane 3 and NOT load-bearing for
     Lane 1.
   * Refresh the §Bottleneck statement: the in-repo half is closed;
     the remaining bottleneck is the offline half of Pillar E (TYPES /
     CPP submission, Zenodo DOI mint, library packaging, outreach)
     per `pillar-e-offline.adoc`.
   * Add a §"Lane-level status" footer: all three falsifiable in-repo
     criteria hold, but Lane 1 stays open at lane-policy because the
     load-bearing question (visible + defensible standing) cannot be
     answered without the offline half. The lane is therefore
     IN-REPO CLOSED, EXTERNALLY OPEN; promotion to fully CLOSED waits
     on author-driven submission events.

Build invariant unaffected: doc-only sweep. `agda proofs/agda/All.agda`
+ `Smoke.agda` + the kernel-guard + the guardrail script were verified
clean earlier this session at the post-#156 main tip.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: hyperpolymath

docs/echo-types/MAP.adoc

@@ -326,8 +326,9 @@ each following the honest-bound + matched-negative discipline
 
 * *Walkthrough 1 — certified region-exit audit*
   (`tutorial/region_exit_audit/`). ephapax-L3-style region exit
-  modelled type-level via `EchoLinear.no-section-weaken`. Killer-app
-  candidate per `roadmap.adoc` §Lane 5 second unblocking condition.
+  modelled type-level via `EchoLinear.no-section-weaken`.
+  Formally-accepted killer-app artefact per `roadmap.adoc` §"Closed
+  lanes" (Lane 5 close-out 2026-05-30).
 * *Walkthrough 2 — epistemic erasure*
   (`tutorial/epistemic_erasure/`). 4-seed → 2-key KDF with
   no-section-via-residue lifted from
@@ -340,9 +341,9 @@ each following the honest-bound + matched-negative discipline
   exhibiting the boundary at which type-level recovery flips.
 
 Track-level docs: `tutorial/README.adoc`, plus per-walkthrough
-`README.adoc` files. Lane policy status: see `roadmap.adoc` §Lane 5
-(currently [PARKED] at lane-policy level pending user unpark
-decision; all three walkthroughs landed regardless).
+`README.adoc` files. Lane policy status: see `roadmap.adoc` §"Closed
+lanes" — Lane 5 closed 2026-05-30 via the formally-accepted
+killer-app branch (Walkthrough 1).
 
 == Tooling
 

roadmap.adoc

@@ -140,22 +140,27 @@ Hirsch et al. choreographic types, and substructural Linear Haskell —
 and is that landing both *visible* (paper-form, citable) and
 *defensible* (survives a referee pass)?
 
-*Bottleneck.* Pillar E (the paper) has `[EXPAND]` tags blocking
-submission. The consumer-side abstraction-barrier proof (Track B,
-under Lane 2) is the one new Agda artefact that materially strengthens
-the paper's narrowed-but-honest claim against the "is this just Σ?"
-objection.
+*Bottleneck.* In-repo Pillar E is closed (all `[EXPAND]` tags below
+the ordinal appendix cleared, see below). The remaining bottleneck
+is the *offline* half of Pillar E — TYPES/CPP submission, Zenodo
+DOI mint, library packaging, outreach — which is author-driven
+(`docs/echo-types/pillar-e-offline.adoc`) and not auto-runnable.
 
 *Close-out criterion (falsifiable).* All three hold:
 
-. `docs/echo-types/paper.adoc` `[EXPAND]` tag 2 (related-work pass —
-  Granule / QTT, Uustalu–Vene comonads, coeffects, choreographic types,
-  lens/optic vs witness-transport leg) cleared. *(Tag 1, background /
-  notation primer, cleared 2026-05-20 via PR #73 — section "Background
-  and notation" in `paper.adoc`, covering type-theoretic setting +
-  HoTT fibres + coeffect / graded-modality lineage + thin-poset
-  reindexing modality + notation table, all within the R-2026-05-18
-  narrowing.)*
+. *LANDED 2026-05-26.* `docs/echo-types/paper.adoc` `[EXPAND]` tag 2
+  (related-work pass — Granule / QTT, Uustalu–Vene comonads,
+  coeffects, choreographic types, lens/optic vs witness-transport
+  leg) cleared in PR #120; landed sections §"HoTT homotopy fibres",
+  §"Graded comonads, coeffects, and QTT", §"Lenses and optics (the
+  witness-transport leg)" + the explicit 2-categorical rule-out
+  (`docs/echo-types/decisions/no-2-cat.adoc`). Tag 1 (background /
+  notation primer) cleared 2026-05-20 via PR #73; tag 3 (evaluation —
+  proof-size / cost table, common-upper-bound idiom) cleared in
+  PR #84 (§"Evaluation and discussion"). Tag 4 (ordinal
+  consumer-evidence appendix) is gated on the Lane 3 Buchholz
+  milestone and is not load-bearing for Lane 1 — see paper status
+  banner.
 . *LANDED 2026-05-26.* `proofs/agda/EchoAbstractionBarrier.agda`
   ships the consumer-side free theorem at the affine instance
   (`affine-consumer-cannot-distinguish`) + the raw-Σ counter-program
@@ -169,6 +174,16 @@ objection.
   Honest "What Echo does NOT do" section foregrounds the
   R-2026-05-18 narrowings.
 
+*Lane-level status.* All three falsifiable in-repo criteria above
+hold. Lane 1 remains *open* at the lane-policy level only because
+the load-bearing question ("type-theoretic standing both visible
+and defensible") cannot be answered without the offline half —
+the venue acceptance and DOI mint. Treat Lane 1 as IN-REPO CLOSED,
+EXTERNALLY OPEN; promotion to fully CLOSED waits on the author-driven
+events tracked in `docs/echo-types/pillar-e-offline.adoc`. Do not
+re-open the in-repo half without a *new* `[EXPAND]` task arising
+from referee feedback.
+
 *Artefacts (existing).* Pillars A–D landed (`EchoFiberBridge`,
 `EchoPullback`, `EchoSeparating`, `EchoGradedComonad`, `EchoRelModel`).
 `paper.adoc` and `types-abstract.adoc` exist as LIVING DRAFT and
@@ -379,53 +394,50 @@ priorities (per 2026-05-26) explicitly favour tighter integration.
 not in scope for Lane 4 cross-repo verification work; navigability
 pointer only.
 
-=== Lane 5 [PARKED] — Tutorial / pedagogy
-
-*Unblocking condition.* Lane 1 closes, OR a single "killer
-application" example emerges that justifies a tutorial track on its
-own merit.
-
-*Candidate killer example (suggested 2026-05-26).* A certified
-region-exit audit, modelled on ephapax L3's region-based memory
-discipline, where every `S_Region_Exit` produces a *consumed* Linear
-Echo with a machine-checked audit guarantee. Concrete, ties to an
-adjacent active project, demonstrates the affine-mode discipline at
-a real audit boundary.
-
-*Scope-when-unparking.* `tutorial/` directory with 3 walkthroughs:
-(1) the certified region-exit audit; (2) epistemic erasure (with
-explicit framing: Echo proves no section recovers the key, NOT that
-in-memory bytes are zeroed — conflating these is a category error a
-sceptic will catch); (3) provenance / debugging echo over a small
-state-reconstruction example.
-
-*Scaffold (pre-resolved 2026-05-26).* `tutorial/README.adoc` lands
-the three walkthroughs at design-doc level with their target file
-layouts, honest-bound disclosures, the per-walkthrough Smoke pin
-discipline, and the killer-app-candidate close-out check on
-Walkthrough 1.
-
-*Walkthroughs landed (2026-05-26/27).* The originally-scaffolded
-Lane 5 triplet is now complete in Agda — Walkthrough 1
-(`tutorial/region_exit_audit/`) landed 2026-05-26 as the killer-app
-candidate; Walkthrough 2 (`tutorial/epistemic_erasure/`) landed
-2026-05-27 with the KDF / no-section-via-residue framing;
-Walkthrough 3 (`tutorial/provenance_debugging/`) landed 2026-05-27
-with the section/no-section contrast across three residue layers.
-Each carries an honest-bound disclosure at the top and a
-matched-negative `NotProved-*` ⊤-aliases block at the bottom. The
-tutorial tree builds under `--safe --without-K` with zero postulates
-via `tutorial/All.agda`.
-
-Lane 5 itself remains PARKED at the lane-policy level pending the
-user's unpark decision (per §"Unblocking condition" above —
-either Lane 1 closes or Walkthrough 1's killer-app status is
-formally accepted). The walkthroughs landing did not auto-unpark
-the lane.
-
 == Closed lanes
 
-(none yet — populated when a lane closes per its close-out criterion).
+=== Lane 5 — Tutorial / pedagogy [CLOSED 2026-05-30]
+
+*Close-out route.* The "killer-application" branch of the unblocking
+condition fired: Walkthrough 1
+(`tutorial/region_exit_audit/RegionExitAudit.agda`) is formally
+accepted as the killer-app example. The audit-boundary discipline it
+demonstrates — every `S_Region_Exit` producing a *consumed* Linear
+Echo with a machine-checked guarantee, against ephapax L3's region
+memory model — is the concrete, externally-corroborable
+demonstration the lane existed to surface.
+
+*Closing artefacts (all under `--safe --without-K`, zero postulates;
+both via `tutorial/All.agda` and pinned in per-walkthrough Smoke).*
+
+* `tutorial/region_exit_audit/` — Walkthrough 1, killer-app accepted.
+  Landed 2026-05-26.
+* `tutorial/epistemic_erasure/` — Walkthrough 2 with the KDF /
+  no-section-via-residue framing. Landed 2026-05-27.
+* `tutorial/provenance_debugging/` — Walkthrough 3 with the
+  section / no-section contrast across three residue layers. Landed
+  2026-05-27.
+
+Each walkthrough carries an honest-bound disclosure at the top and a
+matched-negative `NotProved-*` ⊤-aliases block at the bottom. The
+tutorial tree typechecks alongside the kernel suite.
+
+*Retraction-watch.* Walkthrough 2's framing is "Echo proves no
+section recovers the key", NOT "in-memory bytes are zeroed" —
+conflating these is a category error a sceptic will catch.
+Walkthrough 1's audit guarantee is *type-level*, not a runtime
+attestation. Both are baked into the in-file headers; do not
+silently weaken when expanding the walkthroughs.
+
+*Why this counts as a kill, not a deferral.* The lane's original
+phrasing made unparking conditional on either Lane 1 closing OR a
+single killer-app example earning the tutorial track on its own
+merit. The Lane-1 close-out criterion is unrelated to tutorial
+content — Lane 1 is bottlenecked on Pillar E's paper, not on
+exposition. The walkthrough triple, with Walkthrough 1 carrying the
+ephapax-corroborated audit example, satisfies the second branch
+directly. Cross-referenced from `tutorial/README.adoc` (status
+banner) and `docs/echo-types/MAP.adoc` (lane index).
 
 == Gates summary
 

tutorial/README.adoc

@@ -1,32 +1,35 @@
 // SPDX-License-Identifier: CC-BY-4.0
 // SPDX-FileCopyrightText: 2025-2026 Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>
-= Tutorial track scaffold (Lane 5)
+= Tutorial track (Lane 5 — CLOSED 2026-05-30)
 :toc: macro
 :toclevels: 2
 :sectnums:
 :icons: font
 
 [.lead]
-This directory is the scaffold for `roadmap.adoc` §"Lane 5 [PARKED]
-— Tutorial / pedagogy". Lane 5 is still parked; this scaffold
-exists so that when the lane unparks the next session has the
-structure and walkthrough plans in hand and can land Agda directly
-rather than re-deriving the pedagogy.
+Tutorial track for the echo-types identity claim. Lane 5 closed
+2026-05-30 with Walkthrough 1 formally accepted as the killer-app
+example, satisfying the second branch of the unblocking condition
+in `roadmap.adoc` §"Closed lanes" without waiting for Lane 1.
 
 [IMPORTANT]
 ====
-*Lane 5 unpark status (updated 2026-05-27, evening).* Walkthroughs
-1 (certified region-exit audit), 2 (epistemic erasure with honest
+*Lane 5 status (updated 2026-05-30).* CLOSED. Walkthroughs 1
+(certified region-exit audit), 2 (epistemic erasure with honest
 bound), and 3 (provenance / debugging with layer-1 section + layer-2
 no-section) are all LANDED. The originally-scaffolded triplet is
-complete in Agda. Walkthrough 1 was accepted as the killer-app
-candidate per `roadmap.adoc` §"Lane 5 [PARKED]" second unblocking
-condition. Walkthrough 2 followed as the second realisation,
-addressing the "does echo-types prove key zeroing?" category-error
-question. Walkthrough 3 lands the dual: a *positive* recovery
-result at layer 1 paired with the negative at layer 2, making
-explicit which residue layer carries the load-bearing information
-for source reconstruction in a small fixed domain.
+complete in Agda.
+
+* Walkthrough 1 is the formally-accepted killer-app artefact per
+  the second branch of `roadmap.adoc` §"Lane 5 [PARKED]" unblocking
+  condition (closed-out 2026-05-30 in `roadmap.adoc` §"Closed
+  lanes").
+* Walkthrough 2 follows as the second realisation, addressing the
+  "does echo-types prove key zeroing?" category-error question.
+* Walkthrough 3 lands the dual: a *positive* recovery result at
+  layer 1 paired with the negative at layer 2, making explicit
+  which residue layer carries the load-bearing information for
+  source reconstruction in a small fixed domain.
 
 The Smoke gate (`proofs/agda/Smoke.agda`), the top-level
 `proofs/agda/All.agda`, and the identity-claim gates still do not
@@ -209,22 +212,20 @@ verbatim:
   disclosure is the same discipline as the R-2026-05-18
   narrowings).
 
-== Killer-app close-out check
+== Killer-app close-out (ACCEPTED 2026-05-30)
 
-`roadmap.adoc` §Lane 5 records the second unblocking condition
-("a single killer-application example emerges that justifies a
-tutorial track on its own merit"). The certified region-exit audit
-(Walkthrough 1) is the candidate. Whether it *constitutes* a
-killer-app for Lane 5 unparking purposes is a judgment call the
-user can make when reviewing this scaffold. The candidate's claim
-to killer-app status rests on the three items in §"Walkthrough 1
-> Why this is the killer-app candidate". If the user accepts the
-candidate, Lane 5 can unpark on that basis without waiting for
-Lane 1's other closure.
+`roadmap.adoc` §"Closed lanes" records the killer-app branch of the
+unblocking condition as fired: Walkthrough 1
+(`tutorial/region_exit_audit/RegionExitAudit.agda`) is formally
+accepted as the killer-app example. The acceptance rests on the
+three items in §"Walkthrough 1 > Why this is the killer-app
+candidate" — concrete audit boundary, ephapax-L3 corroboration,
+machine-checked Linear-Echo discipline. Lane 5 closed on that basis
+without waiting for Lane 1.
 
 == References
 
-* `roadmap.adoc` §"Lane 5 [PARKED] — Tutorial / pedagogy"
+* `roadmap.adoc` §"Closed lanes" — Lane 5 close-out entry
 * `CLAUDE.md` §"Ecosystem context" — ephapax row
 * `proofs/agda/EchoLinear.agda` — `LEcho`, `weaken`, `no-section-weaken`
 * `proofs/agda/EchoResidue.agda` — `EchoR`, `collapse-to-residue`,