# Isis Generated Asset Quality Gate

## Scope

V2 treats `v2.cosmetic.*`, `v2.stage.*`, and `v2.decal.*` `isis.asset.generated`
payloads as shipping-asset candidates. Those candidates cannot reach Bellona
cook until `@v2/oshun-adapter` validates a passed
`v2.isis.generated-asset.shipping-quality-gate` attestation for the same source
`contentHash`.

## Required Gate Family

The gate is launch-blocking and requires all of these package results to be
present and `passed`:

- `@isis/anomaly-detection`
- `@themis/music-shield`
- `@themis/visual-shield`
- `@themis/text-shield`
- `@themis/video-shield`
- `@themis/design-shield`
- `@kuanyin/precognition`

The Themis Originality Shields family is wired for V2 through
`@v2/themis-originality-shields`. V2 still blocks Bellona acceptance on any
missing, failed, blocked, review, or `planned_unavailable` shield result.

## Bellona Acceptance Contract

When the gate passes, the Bellona cook command carries:

- `qualityGateRequired: true`
- `anomalyDetectionRequired: true`
- `themisOriginalityShieldsRequired: true`
- `kuanyinPrecognitionRequired: true`
- `acceptGateBlocksLaunch: true`
- the full quality gate attestation evidence bundle

If the quality gate is missing or does not match the source hash, the adapter
dead-letters the event and does not enqueue `bellona.cook.enqueue`.