Private reference

Discord readiness

Launch and operational status from the controlling project records.

Sources: PROJECT_CAPABILITY_REGISTER.md · discord_bot/README.md · Last refreshed: 2026-09-23T23:42:08Z

Readiness status

These are source-qualified readiness records. They do not assert that a Discord launch, player publication, or live proof has occurred.

Capability C30

Actual private Discord publication: correct access, reviewed posts/portraits/rules/map links/pins and receipts

Pending

Bot/publication/host; PIL D01/S06. Exactly two rules/reference entries and standing publication requirements; actual readback, not mocks.

Capability C31

Actual connected sample play and recovery across two sessions

Pending

Bot/test participants/reviewer; PIL D02/D03 and ANA A04. Show NPC/inventory/progression/later consequences; measure waits; observe retry/reconnect without disturbing existing adventures.

Operational controls

Launch and publication require reviewed material and actual Discord readback.
Asset readiness is a required launch gate; local readiness does not establish a Discord upload.
Maintenance preserves current saved controls and does not alter historical controls.