01What exactly is the narrative layer?+
StoriPlay is an experience layer that sits between an AGLC-licensed operator's platform and the player. The operator keeps its own odds, markets, wallet, and settlement; StoriPlay wraps the session in a twelve-stage story arc, decides which stage the player is in, and renders the right screen for that moment, an onboarding beat, an odds-literacy explainer, a reality check, a cooldown, or a closing ledger.
02Why would AGLC want a layer like this in the market?+
Because it converts player-protection policy into a consistent, observable product standard. Rather than assessing each licensee's bespoke implementation, AGLC can look at one arc, one set of named protection stages, and one stream of adherence data across every operator that adopts it.
03How does it integrate with an operator's existing platform?+
Through a REST/webhook API and an embeddable front-end SDK. The operator streams session events (login, deposit, stake placed, outcome settled, session end) to StoriPlay; StoriPlay returns the current stage and the UI payload to render. Nothing about the underlying wagering engine changes, and there is no migration, a pilot typically runs on one vertical for six weeks alongside the operator's normal experience.
04Does StoriPlay handle money, bets, or player funds?+
No. StoriPlay never takes a wager, holds a balance, or touches settlement. It reads session signals and writes experience. That keeps the licensed operator squarely in control of every regulated financial function while the narrative layer handles engagement and player-protection moments.
05What does the twelve-stage arc actually do for retention?+
It replaces the endless loop with a beginning, a middle, and an end. Stages 1–2 set the session's intent, 5–9 carry the play itself, and 10–12 land it. Players return for the next chapter rather than the next spin, and because sessions have a designed close, average session quality rises even when average session length does not.
06What does 'AGLC alignment' mean in practice?+
It means every player-protection expectation an Alberta licensee must meet is expressed as a named, unskippable stage rather than a settings page. Pre-commitment lives in Stage 3, informed-choice and odds transparency in Stage 4, the in-session reality check in Stage 7, the post-outcome cooldown in Stage 10, and self-assessment plus one-tap help and self-exclusion access in Stage 12.
07Is StoriPlay approved or endorsed by AGLC?+
No. StoriPlay is an independent product concept from Storibot.ai and is not affiliated with, reviewed, or endorsed by AGLC. We design to published Alberta standards and to responsible-gambling best practice, and any deployment would be certified through the licensed operator's own regulatory process.
08Can the protection stages be turned off or A/B tested away?+
Not by design. Stages 3, 4, 7, 10, 11, and 12 are load-bearing in the arc: the story cannot advance without them, so they cannot be quietly optimised out of the funnel. Operators can tune copy, timing thresholds, and visual treatment, but not the existence of the stage.
09How is player data handled?+
StoriPlay works from session-level signals rather than identity. Data stays within Canadian residency, is scoped to what a stage needs to decide, and the operator remains the data controller. Every protection prompt and every player response is logged so the operator has an auditable trail for regulator reporting.
10What can AGLC and operators measure?+
A pilot is instrumented on both sides of the trade-off: session completion, chapter-return rate, and net retention alongside limit-setting uptake, reality-check acknowledgement, cooldown adherence, self-exclusion access, and complaint volume. The thesis is that these move together, not against each other.
11How do we start?+
Email info@storibot.ai or mike@storyboxcreative.ca. A short briefing walks AGLC through the arc and the audit model, then a six-week pilot with a willing licensee demonstrates the twelve-stage engine against real retention and responsible-play metrics.