WeaveLayer · Mainnet program · contingency map

What we do if something breaks

Each scenario names the signal we watch, the first moves, who owns them, which gate it threatens, and the decision leadership has to make. Pick any option to see what follows from it; the decision log collects the choices. Scenarios marked Pushback cover what happens if leadership or a stakeholder rejects one of the decisions below. Click a gate to see its readiness criteria and the scenarios that can fail it. Weeks are counted from program start (Week 1) to Mainnet at the end of Week 12.

Program board (GitHub Projects) All issues

12 weeks, 4 gates

Watch window of selected scenario Gate

Decisions already taken (each has a pushback scenario)

  • Feature B is out of Mainnet scope (#32).
  • Audit runs in two parts: stable components first, API after freeze (#12).
  • Partner Beta: time-boxed diagnosis by Nina, Alex stays off it (#29).
  • Partner Gamma: told this week we are scoping, answer at Day 10 (#31).
  • Bug bounty: plan to go live after fixes are validated, with "announced before, live at launch" pre-approved as fallback.

When any gate fails, leadership picks one

  • Same date, less scope: launch what passed the gate, the rest follows.
  • Limited launch: Mainnet with restricted access or capacity limits.
  • Move the date: with a new date tied to the next gate.
  • Or say it plainly: not achievable with the current people, scope, spend and date. Leadership picks which constraint changes.

CEO decides. TPM brings the options with what each costs, CTO gives the technical call.

How to read the labels

  • Data pack the trigger or fact comes from the brief.
  • Assumption my planning assumption, to confirm with the owner in Week 1.
  • Issue numbers link to the program board.