Affiliate

FAQ

Answers to common questions about PAR architecture, verification, identity, evidence, privacy and access.

Evidence-awareAuthority-awareLifecycle-aware

Purpose

One function. Explicit trust boundaries.

Affiliate participation is an approved commercial relationship with explicit attribution, commission and compliance terms.

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

FAQ lifecycle.

Approved affiliate onboarding

Attributed acquisition

Qualification event

Commission validation

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

FAQ