Publication Gate

Purpose

The publication gate defines the minimum trust surface for generated content before it appears publicly.

Required Checks

• Generated content has a visible AI label.
• The source object is mapped where a source exists.
• New generated content has a generation record where Prompt Orchestra is used.
• The output has an appropriate content type and source object type.
• Public copy follows the claims standard.
• Any known limitation is either resolved or acceptable for publication with clear provenance.
• The content class is known in the content and surface inventory.
• The official parliamentary record is not presented as a Parliament People endorsement.
• The review path is clear for the content class and risk severity.
• Material editorial curation, ranking, grouping, or labelling risks have been considered.
• Any report, correction, or source concern attached to the item has been resolved, deferred with rationale, or escalated.

Epic 8 Launch Triggers

Before launching a new content class, source feed, AI transformation, ranking mechanism, public reporting flow, or user-interaction feature, the team should update the inventory, risk taxonomy, queue mapping, claims review, and transparency-log decision.

Comments, debate threads, opinion posts, user annotations, reactions that affect ranking, personalised feeds, sharing, and search-like discovery expansion require a fresh trust and safety assessment before launch.

Transparency-Log Decision

If the publication changes how AI use, provenance, or correction behaviour is presented to users, the release should include a transparency-log decision.