Jollibee Rewards

Operator console · prototype

The console Jollibee's marketing and loyalty team run the programme from — the web app behind PRD-0007's stories. Every change previews before it is applied and needs a reason: there is one write path, under your role, landing in one audit log. No charts — analysis belongs to Prism.

Open

Open the console

Lands on Overview — a work queue, not a dashboard. Every change previews in the panel on the right before it is applied, and needs a reason.

Programme configuration

All 27 settings, each showing its type, permitted range and shipped default — and which ones Jollibee has never decided.

Reward catalog & the A5 problem

Point costs, and the reward-cost arithmetic against the 1.0–1.4% target — with the breakage assumption printed beside it and the two benchmarks that disagree.

Held scans

The review queue Feature 3 needs and Feature 2 says is off. Each scan carries the observations a rule would read — counts and multiples, not scores — as evidence a human can defend.

Fraud rules

Six rules, every threshold unset. Threshold, action on breach, scope and effective date — the four PI-8 names. Sign in as Loyalty Ops and a change is drafted, not applied.

Audit log

Every consequential action — actor, subject, change, time and the reason given. Append-only, and filterable by who.

How to view

Just open the file: double-click app.html. No build step, no npm, no key — nothing here calls out.
Serve it: ./serve.sh (or python3 -m http.server 8080) then http://localhost:8080/app.html.
Switch role: the dev harness along the bottom carries a role switch — the only way to see that out-of-scope subjects are absent rather than refused.
Docs: README · AI-GUIDE · CONSOLE-VOICE · BUILD-LOG · spec at UX-0007.