07 — Supertrack G: RP-06 same-human slot-scope review

Verdict: RP06_VERIFIED (advisory RP; structural mechanism sound). Hash-binding of the slot is via scope_hash and is strengthened by P-02.

Codex delivered (doc 03, and CP-09 doc 10): blanket UNIQUE(activation_id,human_identity_id) rejected as over-blocking; one-occupant-per-slot enforced by exact slot-scoped UNIQUE keys; a generic constraint trigger / readiness guard joins occupied identities to ACTIVE principal_separation_manifest rows.

Checklist

Criterion	Result	Basis
no blanket UNIQUE(activation_id,human_identity_id)	✅	explicitly rejected
slot-scoped UNIQUE (or equivalent) is clear	✅	signoff_binding UNIQUE(activation_id, quorum_profile_id, required_principal_class_id, slot_ordinal, action_id, scope_hash); quorum_vote UNIQUE(activation_id, quorum_profile_id, required_principal_class_id, slot_ordinal)
principal_separation_manifest drives separation	✅	guard joins occupied human identities to ACTIVE must_differ rows; class pairs/counts/slots/scopes are manifest rows, never trigger literals
legitimate multi-role participation not over-blocked	✅	"non-separated roles may legitimately repeat"
same-human abuse remains blocked	✅	same human on both sides of a must_differ pair in one activation/action scope rejects; duplicate occupant in one slot rejects
H04 / signoff hash includes relevant instance rows	⚠️ partial	H04 already hashes reviewer_human_identity_id/binder_human_identity_id (bound identities ARE hashed ✅); the slot (ordinal/class) is bound only through scope_hash, whose composition is unpinned → see P-02

The one tie to P-02

H04's published key list omits slot_ordinal/required_principal_class_id/quorum_profile_id, justified by Codex only "if scope_hash canonically includes quorum profile, principal class, slot ordinal, and action." Until scope_hash's composition is pinned (P-02), the claim that the slot is hash-bound is asserted, not demonstrated. The structural UNIQUE/separation enforcement does not depend on this and is sound; but the hash-binding completeness of RP-06 rides on P-02. Fixing P-02 closes both the H04 byte-implementability gap and RP-06's slot-hash-binding argument in one edit.

Conclusion

RP-06 (advisory) is resolved structurally. Recommend P-02 (pin scope_hash composition) to make the slot-binding provable, not merely asserted.