PRISM v2.18.0 — Lifecycle & deliverables

MINOR, additive (no construct renumbering). Slice 4 of the dependency-ordered
sequence: closes the engagement lifecycle and codifies the deliverable, building
on the 2.16 lanes/Desk backbone and the 2.17 dispatch round-trip.

Surface

• Engagement closure (new §6.7). The symmetric gate out of an engagement —
  a three-layer close sweep (object / lane-meta / operator) that bookends Setup's
  three-layer readiness, opposite in direction and lighter in machinery (a
  verification sweep, not a probe battery). Layer 1: every pass closed-or-deferred,
  falsifiers checked, the verdict shipped as the comprehensive report, polish only
  on a validated deliverable, shipped == validated. Layer 2: every lane's inbox
  drained (the orphan-sweep, now a gate) and the reconcile-at-close codification
  sweep. Layer 3: explicit operator close ratification + externally share-ready.
• The engagement deliverable, codified (new reference/report-architecture.md,
  Appendix K). The comprehensive final report named as the deliverable of
  record — verdict-first, executive-scannable, all work reflected, tight body +
  curated appendices, a linkable "Created with PRISM" credit, a plain-language
  methodology & disclosures section. The canonical body skeleton, the ~11 craft
  conventions (in-one-breath takeaways, how-to-read orientations, the ●/◐/○
  status-glyph legend with Confidence + Verification as separate axes, visual
  scenario-fencing, visible recompute, a self-decoding glossary), the interactive
  workbook cockpit pattern (editable cells → a live decision gate; SP-18
  tie-back), the presentation house-style (HTML→PDF done well; polish only
  validated; inspired-not-impersonating — a closure convention, not a new SP),
  and the reconcile-at-close checklist.
• Deliverable bump-atomicity (§11.2). Bump atomicity now governs the
  client-facing deliverable: cosmetic + text corrections bump too; the shipped
  revision must equal the validated revision (a post-validation correction
  re-stamps + re-validates-if-material); one current file per revision. The IVD
  (§4.14) validates the complete deliverable. An SP-18 deliverable-transform guard
  (§10.1.9) tokenizes standalone figures only so a clarity edit doesn't trip a
  false figure-drift halt; HTML→PDF render hazards in reference/vendor-parsing.md.
• External share (new reference/external-share.md, Appendix L).
  One-repo-per-engagement, externally share-ready by close; the de-coded share
  archive (logical tree + descriptive filenames over SP-14 + a root Index.html,
  expansive to show the rigor); operator-selectable share modes (present-only
  vs repo-committed · report-in-archive vs separate · 2- vs 4-file send); and the
  invariant image-redaction procedure (visual pass → rebuild from PII-safe
  screens → content-hash-verify → grep→0). The read-the-repo-not-the-mirror
  canonical-source rule ties SP-8 (§10.2.1).
• Operator guide (MO-6). Multi-lane session legibility — rename
  <plain name> | <Lane>-<N>, suffix superseded sessions _Archived;
  name-disambiguation relies on the explicit manual-rename step (a summarizing
  surface drops the moniker), with a flag-fatigue note.

Calibration / report back

• Does the closure gate actually catch loose ends (un-drained inboxes, unchecked
  falsifiers, shipped≠validated) before an engagement is declared done?
• Does reconcile-at-close convert the applied-but-not-codified pattern into a
  standing close-time habit, or does craft still accrete uncodified?
• Is the report-architecture bundle enough for a fresh session to build a
  verdict-first report without re-deriving the craft conventions?

Provenance. Lens Library unchanged (v0.15). Snapshot PRISM_v2_18_0.md
(byte-identical at the v2.18.0 tag). Reference detail in the new Appendix K /
reference/report-architecture.md and Appendix L / reference/external-share.md.
Source specs (Engagements clone): ENGAGEMENT_REPORT_v1 (ER-A/ER-K),
ENGAGEMENT_WORKBOOK_v1, ML-63/72/78/96/108, ML-81/89/91/92, R6/R7. Decisions B
(presentation = closure convention, not an SP) and E (reconcile-at-close =
closure-gate line + report-architecture checklist, not a Monitor/SP) applied;
E was the genuinely-open decision — flagged to the operator for ratification.

---

Part of the PRISM v2.15.0 → v2.19.0 promotion arc. See RELEASING.md.