PP ↔ SSSR HECATE rule set
Rule Table
| Rule | Requirement | Gate | Initial severity |
|---|---|---|---|
PP-SSSR-001 | Referenced sssr_signal_id exists in zar.signal_registry | Core Integrity | Critical |
PP-SSSR-002 | Referenced signal has a physical binding | Core Integrity | Critical |
PP-SSSR-003 | Active PP binding carries a CMID | Core Integrity | Critical |
PP-SSSR-004 | Binding CMID equals signal_registry.cmid | Core Integrity | Critical |
PP-SSSR-005 | sssr_reference_template.target = sssr_signal_id | Core Integrity | Critical |
PP-SSSR-006 | Physical target resolution is deterministic | Core Integrity | High |
PP-SSSR-007 | PP binding references a pinned, resolvable PP-MAP | Core Integrity | Critical |
PP-SSSR-008 | Semantic binding contains no static Runtime row_id | Core Integrity | Critical |
PP-SSSR-009 | Semantic binding contains no static tenant/client scope_id | Core Integrity | Critical |
PP-SSSR-010 | Binding temporal/lifecycle state is coherent | Core Integrity | High |
PP-SSSR-011 | Target signal/binding is operationally eligible for requested Runtime use | Runtime Activation | Critical |
PP-SSSR-012 | CMID resolves to zar.cmi_registry | Governance Completeness | Moderate initially |
PP-SSSR-013 | CSI binding exists where required by profile | Governance Completeness | Profile-specific |
PP-SSSR-014 | USO type binding exists where required by profile | Governance Completeness | Profile-specific |
Regulatory temporal semantics boundary
pp.regulatory_temporal_profile and pp.regulatory_applicability_period remain Pergamum Pulse regulatory-knowledge persistence. They do not become SSSR semantic identities and they do not change the constitutional separation between PP and SSSR.
PP-SSSR-010 SHALL continue to validate the temporal and lifecycle coherence of the bridge projection itself (pp.sssr_binding_projection.valid_from, valid_to, recorded_at, superseded_at, status). It SHALL NOT infer legal entry into force, regulatory applicability, reporting-period applicability or legal status from SSSR or from bridge timestamps.
Where an approved PP-MAP, projection, or Runtime release depends on regulatory applicability, the applicable PP object version and its regulatory-period evidence SHALL be resolved upstream in Pergamum Pulse before the bridge is projected or activated. The PP↔SSSR binding remains version-pinned and operational; it does not decide which legal regime applies.
The new PP tables and any material columns MAY/SHALL be registered in SSSR under the existing Core rule for SSSR registration of PP itself where those physical fields are intended to be discoverable or addressable as ZAYAZ signals. Such SSSR registration provides physical addressability only; it does not transfer regulatory-semantic authority from PP to SSSR.
A future PP-native HECATE regulatory-temporal profile SHOULD validate cross-field legal-event and applicability-period consistency. That validation belongs to Pergamum Pulse conformance, not to the PP↔SSSR bridge rule set.