S16 · Production backend and live Discord operation
Implemented components; full stream acceptance is not yet demonstrated.
Current implementation: The gateway and local account service use persisted identity/state; public docs use HTTPS/CDN hosting and agent workers have supervision.
Outstanding acceptance: Large-load Discord delivery, game-host recovery, off-host backups and world concurrency need production validation.
The four requirements below preserve the original release target. Their historic baseline is not used as a current completion score. This page does not mark the entire stream complete merely because related components are installed.
Reference
| Requirement | Required deliverable | Acceptance standard |
|---|---|---|
| S16.01 · Deploy identity and authenticated interfaces | Implement deployment configuration, secret management, account recovery, correct player binding and moderator access separation. | Local seat switching, manual time advancement and developer-only routes are unavailable to production players. |
| S16.02 · Engineer durable concurrent state | Choose and implement production persistence, economic atomicity, scheduled work, event ordering and request deduplication for the defined workload. | Contention tests and recovery show one economic effect per command; technology choice alone is not the acceptance evidence. |
| S16.03 · Exercise Discord delivery at real load | Deploy signed interactions, acknowledgment/defer paths, rate-limit-aware queues, stale-control refresh and public/private boards. | Actual clients and a staging application meet platform requirements and preserve gameplay under delayed or failed message delivery. |
| S16.04 · Build monitoring and operational recovery | Implement alerts, useful logs, backups, restore drills, regional/service failure handling and safe incident interventions. | Restoration is exercised; software rollback does not silently reverse innocent player trades; staff can investigate without ad hoc inventory edits. |