Policy, jurisdiction and time bindings
WAGECODE uses separate policy, jurisdiction and time bindings to locate wage-state meaning within declared rule, domain and temporal conditions.
Policy binding
policy_binding is the WAGECODE-aligned relationship that binds a computation, object, fact set, function, attestation, registry event, reliance event or artefact to the policy version, rule source, authority context and effective period under which it is interpreted.
Short form: the declared relationship connecting a wage-state operation or object to its versioned policy source, scope and effective period.
Jurisdiction binding
jurisdiction_binding is the WAGECODE-aligned relationship that binds a wage-state object, computation, fact set, function, attestation, registry event, reliance event or artefact to the jurisdiction, legal domain, institutional domain, sectoral domain, territorial scope or authority scope within which it is interpreted.
Short form: the declared jurisdictional or domain context within which wage-state meaning is interpreted.
Time index
time_index is the declared temporal interval and basis used to locate a wage-state computation or object in time, comprising a start, an end and the basis according to which the interval is interpreted.
A time index comprises:
- start
- end
- basis
time_index is not the same as issuance_timestamp, upload time, observation time, document date, payment date or current date.
How the bindings interact
Policy, jurisdiction and time bindings are separate but jointly locate wage-state meaning. They are three concepts grouped for reference, not a single combined entity.
Replay and supersession
Bindings are recorded so that a computation or object can be replayed under the policy version and interval that applied, and superseded when those conditions change.
Boundaries
These bindings are not legal advice, not certification, and do not determine jurisdictional or regulatory outcomes.
Source registers
This page provides a controlled public reference to WAGECODE v1.0. It does not reproduce, amend or replace the complete published specification. Where any difference arises, WAGECODE v1.0 controls.
WAGECODE implementation independence and conformance do not grant or imply a licence to CWSO Authority proprietary runtime assets. Protocol conformance, runtime-asset authorisation and affiliation are separate questions.