docs/runbooks/launch-checklist.md — governance, treasury, hooks, router trust #67
Labels
No labels
agent:fix_bugfix
agent:fix_conflicts
agent:fix_security
agent:gap_analysis
agent:implement
agent:implement
agent:implement
agent:open_issues
agent:ready
agent:research
agent:security_audit
agent:verify
architecture
backend
blocker:hybrid
blocker:launch
blocker:limit-orders
blocker:v2
block:log_only
block:security
bug
ci
contracts
correctness
deploy
dev
devops
docs
documentation
duplicate
e2e
enhancement
epic
feature
frontend
functional-completion
gas
good first issue
governance
help wanted
high-risk
hooks
hybrid
indexer
infra
infrastructure
integrators
invalid
launch-blocker
limit-orders
localnet
localterra
low priority
missing-implementation
needs-design
ops
performance
priority
high
priority
medium
product
qa
QA
question
ready
ready
research
scripts
security
security-hardening
smartcontracts
tech-debt
testing
ux
UX
v2
verification
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
code/cl8y-dex-terraclassic#67
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type
missing-implementation (operations)
Evidence
docs/deployment-guide.md,docs/security-model.mdREVIEW.md§9 fastest path v2Rationale
Reduces governance footguns (hooks brick swaps, wrong treasury).
Dependencies
None.
Acceptance criteria
Epic
#57
marked this issue as related to #57
Added
docs/runbooks/launch-checklist.mdwith phased pool-only (v2) steps: governance/treasury, hook policy, trusted router, tier/registry verification, and pointers to the smoke script and security model. Linked from the deployment guide (top) and security model. @brouie Please verify the runbook matches your operational expectations for go-live.@PlasticDigits Verified on current main. Acceptance criteria:
Runbook matches operational expectations for go-live: addresses governance footguns, hook policy, wasm policy, trusted router setup, and post-deploy verification for pool-only v2. Closing.