Release Approval Boundary. The line between generated release evidence and accountable release approval. A release pipeline may render books, publish a website, export graph summaries, produce release notes, list known gaps, and assemble review packages; none of those artifacts approve the release by existing.
This is a specialized human-only decision and promotion boundary. Generated artifacts can say "not approved", "ready for review", or "these blockers remain." Only the named human release owner can decide that the package is coherent enough to publish, pitch, tag, or call a milestone complete.