The provider.
The sponsor or capacity-holder funding the voucher. Their commitment is recorded, their attribution is preserved, their cost is bounded by the policy under which the commitment was made.
Extensions / 3.1
SLAM XP — Dormant value activation.
SLAM XP activates dormant value across sponsors, operators, partners, recipients and the surrounding ecosystem — under deterministic governance, with privacy preserved by architecture and authority preserved by the chain.
01What SLAM XP is — and is not
SLAM XP is the value-flow extension of H.A.R.I. It is the layer that converts dormant capacity (sponsor budgets not yet routed, partner inventory not yet activated, territorial benefits not yet delivered) into governed value flowing to defined recipients. The conversion happens deterministically; the governance happens through the same kernel and forensic chain as any other H.A.R.I. operation.
SLAM XP is not a loyalty program. It is not a customer-data product. It is not a scoring engine for recipients. It is not a cryptocurrency or token system. It is a deterministic value-flow protocol that respects the recipient's privacy and the sponsor's accountability simultaneously.
02The IX Algorithm — deterministic value conversion
The IX Algorithm is the deterministic conversion at the heart of SLAM XP. Given a defined input (a sponsor commitment, an operator capacity declaration, a partner inventory release) and a defined target (a recipient class, a territorial scope, an operational window), the IX Algorithm produces a deterministic conversion: a set of governed vouchers, each carrying scope, lifecycle, and attribution metadata sufficient to govern its full lifecycle.
The same inputs produce the same set of vouchers, every time. The conversion is fully traceable: which sponsor commitment produced which vouchers, under which policy, for which target — written to the chain.
03The POL Protocol — transaction resilience
The POL Protocol governs the transactional integrity of voucher lifecycle events. Issuance, activation, consumption, expiration, and revocation are atomic operations under POL: each is either fully written to the chain or not written at all. There is no partial state. There is no orphan voucher. There is no consumption without a corresponding issuance.
The protocol's design property is conservative: under load, under partial failure, under network degradation, under any adversarial pattern that affects throughput, the chain is consistent. SLAM XP refuses to produce a voucher event that cannot be cleanly recorded.
04The Five-Win constraint — non-negotiable
SLAM XP refuses to operate any voucher flow in which a participating party is forced to lose for another to win. The constraint is structural: it is encoded in the IX Algorithm and enforced by the kernel. The five parties to the constraint are:
The territory.
The geographic or jurisdictional scope where the value flows. The territory's authorities — municipal, regional, or operational — receive a chain-backed record of the impact within their scope.
The partner.
The operator delivering on the ground. Their delivery is recorded against their attribution; their margin is preserved by the IX Algorithm's deterministic pricing.
The user (recipient).
The recipient of the value. They are not profiled, not scored, not converted into a marketing surface. They receive the benefit, they consume or decline, the chain records the event.
The ecosystem.
The surrounding environment, market, or community. Externalities are accounted for in the policy: a SLAM XP flow that would impose a negative externality is rejected by construction.
All five must win, or the flow does not happen.
Encoded structurally in the IX Algorithm. The constraint is not an aspiration — it is the gate that any candidate flow must pass before issuance.
05The SCINTILLA model — push-only, system-initiated, non-gamable
The SCINTILLA model defines the relationship between the platform and the recipient. Three properties define it.
- Push-only. The recipient does not pull value from SLAM XP. There is no "claim," no "cash in," no recipient-side action that triggers issuance. Issuance is system-initiated under the IX Algorithm, scoped by the sponsor commitment and the territorial policy. The recipient's surface is reception, not extraction.
- System-initiated. The platform decides, under deterministic policy, when a voucher is issued and to which recipient class. Recipients do not opt in to a profile. Recipients do not opt in to a scoring system. The system reaches the recipient under defined preconditions; the recipient receives.
- Non-gamable. The IX Algorithm's determinism means the conversion cannot be gamed by recipient behaviour. There is no metric a recipient can optimize to receive more. There is no engagement loop for the recipient to be "captured" by. Engagement is not the goal; deterministic value delivery is the goal.
06Voucher lifecycle
A voucher passes through six possible states, each transition written to the chain under POL. The lifecycle is closed: there are no states outside this set.
07First pilot vertical: healthcare patient housing
The first SLAM XP pilot is patient housing in healthcare. The shape: sponsors commit accommodation capacity (typically with under-occupied off-peak windows); SLAM XP issues vouchers under deterministic policy to patient households whose treatment requires travel; vouchers activate when the household confirms a stay; consumption is recorded as the stay completes.
The chain delivers the sponsor's ESG record, the operator's delivery record, and the patient household's benefit — all without retaining patient PII beyond the role-token mapping required by governance. See Healthcare & clinical trials for the operational frame.
Key principle
Back to top
H.A.R.I. governs. SLAM XP activates dormant value. The two are architecturally separable; SLAM XP cannot operate without H.A.R.I.'s deterministic governance underneath, and H.A.R.I. operates entirely without SLAM XP in the verticals that do not need it.