Operations
Technology operations workspace. Every figure below is derived from the canonical layer. Nothing is keyed by hand.
Shopper read latency, 95th percentile
Write-back queue depth
Manual-effort index, this session
Every residual human touch is counted, including exceptions the platform itself creates.
Reconciliation status
One availability position, every channel
Point-of-sale, ERP, e-commerce, marketplace and community movements all update one canonical position. Each channel reads from it, so a sale at the Paragon till removes the unit from LazMall, TikTok Shop and community storefronts in the same moment.
| Article | Paragon | Woodlands | DC or supplier | Paragon store | Woodlands store | Metro Online | LazMall | Shopee Mall | TikTok Shop | Community | Freshness |
|---|
Shopper simulator
Channel allocation policy
Allocation is configuration, set by Merchandising. No developer is involved.
Correctness under partial failure
State change and its event are written in one transaction. Messages are durable, ordered per article, and consumed idempotently. If a system of record goes offline its write queue holds and drains in order on recovery.
Event pipeline, live counters
Fault injection
Write-back queues
Proof of zero data loss
Reconciliation, canonical position against ERP
Commission, split settlement and reconciliation
Rules are versioned and effective-dated. Every accrual carries the rule version and attribution evidence that produced it, so any payout can be explained months later.
Commission rule set
v1.3Selected accrual, explained
| Order | Ambassador | Type | Article | Line, net of GST | Rule | Commission | Status |
|---|
Settlement by ambassador, current cycle
| Ambassador | Tier | Pending | Cleared | Payout queued |
|---|
Payouts are Metro obligations disbursed by a licensed payment provider. The platform holds no participant float. Dual control applies above S$1,000.
Three-way reconciliation
| Exception | Owner | Status |
|---|
Brand onboarding and purchase order approval
Use case 2 from the Brief. Merchandising onboards UrbanCrafters for a pop-up without an IT change request. When stock runs low a purchase order is drafted, and because it exceeds the approval threshold it goes to the CEO's phone.
UrbanCrafters Pte. Ltd. (example applicant)
Replenishment and approval
| Purchase order | Supplier | Article | Qty | Value | Route | Status | ERP |
|---|---|---|---|---|---|---|---|
| No purchase orders drafted yet. | |||||||
One interface surface, several versions at once
Use case 4 from the Brief. When Phase Two ships crowd-sourced delivery, the new module calls version 2. Store terminals and the logistics partner keep calling version 1 with no change. Both are served from one implementation.
Request console
| Calling system | Version | Calls this session | Status |
|---|
Additive-only change within a major version is enforced by contract tests at merge. A version is retired only after per-client telemetry shows nobody still calls it.
Response
Send a request to see the response, its headers and its timing.
Audit trail
Append-only. Every privileged and financial action is recorded with actor, time and detail. Replays, rule changes and approvals all appear here.
| Time | Actor | Action | Detail |
|---|