boris-video-absorption: three deferred-with-trigger follow-ups need to stay discoverable after slice prune

[kyle-sexton]

This was generated by AI during work-loop execution.

Companion to #1424 Phase A. docs/topics/boris-video-absorption/ is being pruned (all 8 plan
phases [DONE], "Open questions: None blocking"), but its PLAN.md Brief section records three
items the plan deliberately deferred with a trigger condition and explicitly did NOT file as
tracker issues at the time ("recorded in digest slice, NO tracker issues"). Per #1424's Phase A
entry for this slice ("decide explicitly whether any are worth a tracker issue first"), routing
them here as one consolidated item before deletion so the trigger conditions stay discoverable —
none is actionable yet.

Deferred-with-trigger items

1. Verification self-improvement loop. Trigger: accumulated recorded runs (i.e., once enough
   verification:confirm runs have been recorded to learn from).
2. Bounded build→review→fix loop. Trigger: post-Phase-II enforcement rail (depends on
   enforcement infrastructure this plan explicitly placed later than its own scope).
3. Claude Tag enablement. Trigger: post-8/3 cutover + Enterprise admin check.

Disposition

None of the three trigger conditions has fired as of this filing. This issue exists purely so the
three items and their triggers remain discoverable after the source slice is deleted — not an
instruction to act now. Whoever revisits this should re-check each trigger before treating the item
as actionable.

Source

docs/topics/boris-video-absorption/PLAN.md lines 24-28 (Brief section, as of commit dfeb9fc,
before Phase A prune).

[kyle-sexton]

This was generated by AI during triage.

Triage

Redundancy check: no existing tracker item covers boris-video-absorption's three deferred items;
not a duplicate. No docs/out-of-scope/ ledger in this repo.

Verification: confirmed against PR #1459 (merged) and #1424, both of which name this issue as the
routing destination for boris-video-absorption's deferred-with-trigger content, explicitly filed
"before deletion" per #1424's own instruction for this slice ("decide explicitly whether any are worth
a tracker issue first").

Classification:

• Type: Task.
• Priority: low — all three triggers are unfired and depend on external/future conditions
  (accumulated verification:confirm run history; post-Phase-II enforcement infrastructure that this
  plan explicitly placed out of its own scope; a Claude Tag Enterprise-admin cutover). None is urgent
  or blocking other work today.
• State: human-gated — nothing actionable until a trigger fires; noticing a fired trigger and
  deciding whether to act is a human call, not a bounded autonomous task. Kept open for
  discoverability, per the issue's own stated purpose.

Batching determination: see #1464's comment for the shared reasoning across #1464/#1463/#1457 —
same procedural pattern, disjoint content and triggers (verification tooling / build-review-fix loop /
Claude Tag, unrelated to the other two issues' content), no PR/code work to consolidate, so this stays
a separate item.

[kyle-sexton]

Frontier disposition (drain session)

Ruling: Close as completed.

boris-video-absorption deferred-with-trigger follow-ups routed before slice prune; triggers remain unfired.

Re-open trigger: When a boris-video-absorption deferred trigger fires.