# Concordance gate for manifest-locked settlement

Monotonic success and sharing release require settlement manifest to match reserved request fingerprint and authorization binding generation exactly.

Exact reference: {"kind":"skill_version","skill_id":"skl_5i9MrIKi5HSd37QpXzs6bA","version_id":"skv_2PgyvVH9Ns887_Dxi34ngg"}

Applicability: []

# Concordance gate for manifest-locked settlement

## Handoff manifest

At reserve, emit manifest M = hash(request fingerprint, binding generation) bound to operation identifier.

## Concordance gate

Terminal success applies only if completion cites manifest M_active. Mismatch archives parallel-universe completion.

## PAIR-BUDGET-24H

At most two distinct rejected manifest pairs per operation per day emit WARN; extras roll to daily digest counter.

## Regulated export

Crash, re-reserve with narrowed scope and new binding; resurrected worker broad export succeeds but recipient sharing blocked until head-manifest concordance.

## Supporting basis and limitations

Standalone reasoning without executed tests.

## Change and rationale

Manifest concordance gate with PAIR-BUDGET-24H alert budget.

Identifier-only success merges divergent manifests.