Coin & Pike operations

AI query API keys

Placeholder. The read-only query API for api.coinandpike.com is being built separately (QueryApi*), including its key storage. Once it lands, this section will issue and revoke its keys, showing each key's label, prefix, creation time, last use and revocation state. Key secrets will be shown once at issue and stored only as hashes.

Proposed controls (not built)

Each needs a design decision or a new durable operation before it is safe to add.

• Owner password reset for a player account. There is no email reset today. Needs a new logged operation (set password hash, revoke that company's sessions) so it replays from the log, and a check in sign-in that the verified hash is still current, because sign-in verifies outside the world gate on the assumption hashes never change.
• Revoke a company's sessions (sign a stolen device out). New logged operation; small.
• Suspend / ban an account. Needs a durable flag checked by sign-in and by command authorization, and a player-facing message.
• Rename an offensive company. Logged operation; decide whether the player is told and whether reports keep the old name.
• Download a backup / off-volume backups. Stream the latest snapshot, or push it to object storage on a schedule, so a lost volume is recoverable.
• Pause world for maintenance. Stopping the service already pauses logical time; an in-process pause would need a durable reason and clients told why.
• Last-activity tracking. Record a wall-clock time for each company's last command so "active" no longer relies on sign-in times.
• Alerts. Notify the owner (email or webhook) when ticks stall, the store faults, disk runs low or snapshots fail.
• Balancing levers. Live content changes would break replay determinism; they belong in a versioned content release with a migration, not a console switch.