Skip to main content

Goal

Run NodalMerge with repeatable host operations, compatibility confidence, and incident response readiness.

Step 1: Host and persistence baseline

Read and execute: Validate:
  • host health endpoint responds
  • provider inventory endpoint responds
  • restart preserves expected room state in durable mode

Step 2: Security and capability posture

Read: Validate:
  • locked-room token flow works
  • unauthorized control-plane commands are denied deterministically
  • rate-limit guardrails are configured and observable

Step 3: Upgrade and compatibility drills

Read: Validate:
  • canary upgrade checklist can be executed
  • replay/hash comparison workflow is documented for rollback gates

Step 4: Observability and incident workflow

Read: Validate:
  • metrics scraping and key counters are visible
  • close-code and rejection triage flow is known by on-call
  • one incident simulation completed with evidence bundle

Step 5: Platform readiness checklist

  • Durable storage and lifecycle settings are explicit
  • Auth and capability scopes are least-privilege by default
  • Upgrade/rollback runbook is rehearsed
  • Replay and protocol evidence capture is standardized
  • Alerts exist for guardrail and saturation signals