BetConstruct

Decisive acceptance gates

1. PAM-01State authority

   Exactly which player, wallet, session, control, bonus and reporting states does the PAM own?

   Accept only when: Every mutable field has one authority, permitted writers are bounded, and conflicts, replay, correction and audit behaviour pass witnessed tests.

2. PAM-02Interface contract

   Can the PAM operate as a modular service across the required synchronous APIs, events, exports and administrative workflows?

   Accept only when: Buyer tests cover success, duplicate, late, out-of-order, timeout, partial-failure and version-change paths with deterministic recovery.

3. PAM-06Portability

   Can the operator extract a complete operational record and replace the PAM without reconstructing critical state from reports?

   Accept only when: A buyer-run rehearsal reconstructs active and historical state in a target schema, reconciles totals and preserves legally required lineage.

Separate quote lines to require

Decisive acceptance gates

1. SB-02Engine and trading authority

   Who owns the engine, compiles prices, accepts or rejects bets, changes limits and carries trading decisions?

   Accept only when: Every automated and human trading action has one accountable party, a bounded permission, timestamped input and reproducible audit trail.

2. SB-04Feed and event integrity

   How are event identity, feed conflict, latency, suspension, correction and abandonment controlled across suppliers?

   Accept only when: The system detects stale or conflicting data, suspends deterministically, records overrides and reconciles every correction to bets and balances.

3. SB-06Peak resilience and economics

   Can the proposed service and price survive event peaks, feed disruption, settlement bursts and managed-trading escalation?

   Accept only when: Capacity, recovery, support and price are tested against buyer volumes and event shapes, with measurable service levels and remedies.

Separate quote lines to require

Decisive acceptance gates

1. AGG-01Content permission

   Can each proposed supplier, studio, game and aggregator role be used by the operator entity in the target market?

   Accept only when: Every enabled game version traces through the aggregator and studio entities to the required current permissions and operator release approval.

2. AGG-02Wallet protocol

   Is ledger authority, debit, credit, rollback, replay and open-round handling deterministic across every studio adapter?

   Accept only when: Each adapter passes duplicate, timeout, late-result, rollback, resettlement and failover tests without an unmatched balance or round.

3. AGG-03Release inventory

   Can the buyer identify exactly which game binary, math, certificate, metadata, configuration and jurisdiction rule is live?

   Accept only when: The live inventory reconciles to approved versions, changes are buyer-gated, and a single game or version can be disabled and rolled back safely.

Separate quote lines to require

Decisive acceptance gates

1. TK-02Prime delivery perimeter

   Which platform modules and third parties sit inside the supplier's accountable end-to-end service?

   Accept only when: Every launch dependency has one accountable party, an interface owner, an acceptance test and a remedy without gaps between supplier and subcontractor obligations.

2. TK-03Wallet and control authority

   Which system is authoritative for identity, balances, bonus liability, limits, exclusions, transaction history and regulatory reporting?

   Accept only when: One authority is named for every state, conflict resolution is deterministic, and debit, credit, rollback, limit and exclusion tests reconcile end to end.

3. TK-04Launch product set

   Are the exact casino, live, sportsbook, bonus, CRM, fraud and reporting modules production-ready for this configuration?

   Accept only when: Every required module and substitute integration passes the buyer's exact market, version, data-flow and control tests in the proposed environment.

Separate quote lines to require