Community platform — retained operating record

Owner-approved public evidence artifact — reviewed 2026-08-09

Substantiates: community-platform metrics stale-tolerant, unattended-cycles, network-snapshot, and community-content. This artifact deliberately omits the community, partner, account, repository, server, and player identities.

Aggregate record

A committed read-only extractor was run against the retained private service archives:

publisher log: 3,266,695 lines
completed render-and-swap cycles: 231,109
retained server-list snapshot: 41 servers / 54 players online
snapshot date: 2023-11-28
retained community-uploaded thumbnails: 319

The cycle count recognizes the publisher’s terminal Worker done record. The time span is bounded by the publisher repository’s first commit and the log’s last modification date; it is not presented as a continuous-availability measurement.

Mechanisms checked in retained source

Stale response instead of a blank one

The server-list adapter keeps a last-known-good response separately from its five-minute query cache. A non-successful upstream response returns that retained value when one exists; only a successful response replaces it. If no good response has ever been observed, the adapter returns an explicit empty result rather than manufacturing state.

Atomic static publication

The unattended publisher renders HTML and CSS into temporary paths first, then replaces the public files individually with operating-system atomic rename operations. A reader can therefore receive the previous complete version or the next complete file, but not a partially written file.

write(temporary_html, rendered_page)
copy(stylesheet, temporary_stylesheet)
atomic_replace(temporary_html, public_html)
atomic_replace(temporary_stylesheet, public_stylesheet)

Separate payment, membership, and reward boundaries

• Sponsorship checkout metadata is consumed by completion webhooks before the corresponding sponsorship state is updated.
• Membership roles remain the entitlement source of truth and are read through a bounded cache rather than copied into the payment system.
• Vote thresholds create timestamped, expiring reward messages handed to a queue; delivery can lag without blocking vote intake. The retained publisher declares the queue durable, but this extract does not claim that every message survives a broker restart.

Limits and redactions

• No registered-user, total-vote, peak-concurrency, or availability figure is claimed because no primary record for those figures was retained.
• No player record, username, server address, host, endpoint, credential, community name, partner name, repository name, or commit author is included.
• The archive contains legacy identity and credential history and is not a publication candidate. This note is a narrow evidence extract, not a source release.