Institutional reliance
WAGECODE defines institutional reliance on a CWSO through declared purpose, profile, scope and a replayable Reliance Receipt.
Reliance context
Institutional reliance is the point at which a governed wage-state object is used as an authoritative input to an institutional decision or process.
Reliance profile and scope
Reliance profile describes the institutional use context. Reliance scope limits the use for which the CWSO is being relied upon. A use outside that scope is not converted into conformant reliance merely because the same CWSO was available.
Reliance Receipt
A Reliance Receipt, abbreviated RR, is the WAGECODE-aligned record that captures a reliance event, including the relying party, relied-upon object or artefact, reliance purpose, reliance scope, policy-version context, issuer-authority context, restrictions, timestamp and replay or audit references where applicable.
What a Reliance Receipt proves
A Reliance Receipt proves that a declared reliance event was recorded. It does not automatically prove that the institutional decision was legally correct, commercially prudent, regulator-approved, court-accepted or substantively uncontested.
Relying-party responsibility
WAGECODE governs wage-state reliance conditions. It does not make the relying party's lending, insurance, employment, enforcement, regulatory, funding or adjudicative decision.
Reliance examples
The following are informative examples only and do not enlarge the normative reliance framework.
- A lender records reliance on a CWSO for an affordability assessment within a stated scope.
- An insurer records reliance on a CWSO for benefit calculation within a stated policy version.
- An auditor replays a CWSO and its Reliance Receipt to test a prior decision basis.
Boundaries
Reliance is not certification, not legal compliance, and not a guarantee of institutional outcome.
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.