RELAY

Controlled Event Intake

I. Definition

Relay is a settlement-activated event intake layer.

It provides a controlled HTTPS submission endpoint for structured operational data, gated strictly by confirmed Bitcoin entitlement.

Relay persists events deterministically within bounded entitlement scope.

II. Activation

Relay becomes available only after:

1. Invoice generation
2. Settlement to designated address
3. Required confirmation depth
4. Entitlement state transition to ACTIVE

Relay access expires automatically upon entitlement expiration.

III. Entitlement Boundary

Access is capability-bound.

Invoice ID functions as the entitlement reference.

Relay processing is permitted only while entitlement state is ACTIVE.

Entitlement state transitions are confirmation-derived and immutable.

IV. Submission Interface

Events are submitted via:

POST /relay/submit

Each submission must include:

• invoice_id
• tier
• event object

All submissions are evaluated deterministically prior to persistence.

V. Processing Model

• Entitlement state is verified
• Confirmation threshold is enforced
• Event schema is validated
• Event is persisted
• Structured acknowledgment is returned

Event processing is confined to ACTIVE entitlement state.

VI. State Model

Relay entitlement states:

UNPAID → ACTIVE → EXPIRED

Processing is permitted only during ACTIVE state.

State transitions are binary and machine-evaluated.

VII. Execution Discipline

• Settlement-gated
• Confirmation-enforced
• Capability-bound
• Deterministically acknowledged

Relay execution is strictly bounded to settlement-derived entitlement state.