Published / v0.4
Jurisdiction Gate Spec
Feature availability, compliance tiers, and region-aware fallbacks.
- Published
- State
- Published
- Version
- v0.4
- Source
src/content/proofs/jurisdiction-gate-spec.mdx- Digest
sha256:25ea53c87e9e14d8337d8c0f39e41a604e375998de07a8ef4204ec61e81f763b- Scope
- Region-aware feature gating for public and app surfaces.
- Authors
- CRSH Protocol
Claim
Feature availability must be derived from jurisdiction state before restricted actions are exposed.
Minimum Rule
The public page may explain a feature, but the product surface must still gate entry, wagering, or payout behavior by jurisdiction tier.
Audit Trail
When a feature is unavailable, the product should preserve enough state to explain whether the gate came from region, account eligibility, or platform status.