P-03 - H05 And H02 Total Orders

Status: RESOLVED_BLOCKING

Aggregate	Membership	Canonical order
H02 signoffs	signoff rows for the H02 epoch, joined to activation at the same requested epoch; exact ACTIVE required slots	(target_manifest_id, tier_id NULLS FIRST, action_id, quorum_profile_id, required_principal_class_id, slot_ordinal, reviewer_principal_id, signoff_id)
H05 measurements	capability_measurement.run_id = capability_run.run_id; exact sealed requirement set	(measurement_requirement_id, measured_at, measurement_id)
H05 artifacts	capability_artifact.run_id = capability_run.run_id; sealed requirement/count set	(artifact_requirement_id, created_at, capability_artifact_id)
H02 capability hashes	finalized runs for the H02 epoch; capability must be ACTIVE and workload must equal its bound workload; every ACTIVE required capability has a run	(capability_id, workload_profile_id, finalized_at, run_id)
H02 post-activation state	all valid state rows for executed activations whose requested_control_epoch = H02.control_epoch; at least one per executed activation	(activation_id, verifier_principal_id, verified_at, verifier_state_id)

Times normalize to UTC; UUIDs use canonical lowercase text under COLLATE "C"; required order fields cannot be NULL. Missing/extra rows fail. Empty is permitted only when the corresponding required/parent source set is empty under the exact CP-06 rule. Physical row/insertion order cannot affect a digest.