Skip to content

docs: create runbook for common operational scenarios #211

Description

@FaveTeamz

Summary

Operators need step-by-step runbooks for the situations most likely to occur in production.

Runbooks needed

  1. Contract upgrade — build, optimize, upload WASM, call upgrade
  2. Admin key rotation — two-step transfer procedure
  3. Contributor cap emergency increase — requires governance vote + contract upgrade
  4. Incident response — what to do if a bug is found post-deploy (pause strategy TBD)

Acceptance Criteria

  • Each runbook is a standalone markdown file in docs/runbooks/
  • Commands are annotated with expected output
  • Cross-linked from README Operations section

Metadata

Metadata

Assignees

Labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions