Referral
Rewards
Define qualifying events, reward calculation, exclusions, approval and payment status.
Purpose
One function. Explicit trust boundaries.
Referral is distinct from affiliate distribution and follows its own eligibility, attribution and reward rules.
Every material state transition should remain attributable to an authenticated actor, an authority context, a timestamp and the evidence required to reconstruct what happened.
Operational flow
Rewards lifecycle.
01
Generate referral attribution
02
Qualified signup
03
Eligibility check
04
Reward approval
05
Settlement / reporting
Object model
Minimum verification context.
The exact schema can vary by object class and policy version, but the verification layer should be able to resolve these core dimensions.
- Identifier
- Type
- Status
- Authority
- Evidence
- Timestamp
- Relations
- History
Operational state
Designed for progressive activation.
Public layerAvailable
PolicyDraft / publishable
IntegrationExtensible
GovernanceTraceable
Production status must always be sourced from the deployed service and published through System Status; this static package does not claim backend activation.
Related PAR domains