12.2.1 Why this fork exists (and why investors should care)

Chapter 11 establishes that Terra Classic’s primary blockers are institutional (accountability, operator risk, governance execution), not “just technical.” The chain can keep running while still failing the institutional tests that determine whether serious capital, builders, and counterparties will touch it.

Two datapoints make the fork non-optional:

• Governance is high-volume but low-signal and low-conversion. In the Truth Dashboard’s proposals snapshot (since May 2022), pass rate is 9.1%, rejected rate is 82.2%, and median delegators is 0 (866 of 1,711 proposals have zero delegators).

• Participation is structurally thin. The governance participation snapshot shows voter wallets per proposal ~279, and voter wallets as % of active wallets ~0.24%. It also shows meaningful validator non-participation (missed votes share ~39.99%) and that validators with 100% non-participation control a non-trivial share of voting power.

For investors, this is the point: if decision authority is effectively concentrated, responsibility is too. You cannot market decentralization while operating like a small committee with weak execution discipline.

So the system needs an explicit fork—two acceptable outcomes—because the current state is neither a credible turnaround nor an honest admission of incapacity.

12.2.2 The timebox (policy)

Within 3 months, Terra Classic governance must produce one of the following:

• Outcome A: Validators publish a dedicated, professional recovery plan (roadmap) that is realistic, measurable, and executable.

• Outcome B: Validators publish a public statement acknowledging what the data already indicates: the chain is not in good condition and the validator set does not have the expertise/time/will to fix it—and immediately begin recruiting professional operators with accountability.

This is not rhetoric. It’s a go/no-go gate for credibility.

12.2.3 Outcome A — A validator-led recovery plan (roadmap) that is evidence-bound

Outcome A is acceptable only if it is proof-first (evidence-bound), not narrative-first (marketing-bound).

A1) What “professional recovery plan” means (minimum viable standard)

A credible plan must include, at minimum:

1. Named accountable owners for each workstream (not just “the community”).

2. Scope + priorities (what is in / what is out) with sequencing logic.

3. Budget + funding rails (Community Pool, grants, partnerships) mapped to deliverables.

4. Milestones with dates (12–24 months, but with 30/60/90-day checkpoints).

5. KPIs tied to on-chain reality (usage, reliability, market access, security assurance), not vanity.

6. Risk register (institutional risks included: control-plane, key-person, governance capture).

7. Security assurance plan (even if minimal) including explicit acknowledgement of the current post-2022 audit/bounty gap (confirmed fact in this report).

8. Operational system: public project board, release cadence, incident process, comms SLA.

Investor translation: A roadmap without owners, budgets, and measurable checkpoints is not a roadmap—it’s an aspiration deck.

A2) “Proof anchors” (documented) — what investors should demand to see

To prevent Outcome A from degrading into “paper recovery,” the plan must ship with proof anchors that make execution legible:

Governance anchors

• A governance package that states: what will be decided by vote vs what is delegated to operators under mandate.

• A binding commitment to publish decision logs and post-mortems for misses.

Delivery anchors

• A publicly visible delivery system (project board + backlog + milestones) hosted in GitHub (or equivalent), with:

  • issue-to-release traceability,

  • owners attached,

  • weekly progress artifacts.

Accountability anchors

• A single “Recovery Operator” function (could be a committee, but must behave like an operator):

  • one contact surface, one responsibility surface, one reporting cadence.

Measurement anchors

• A minimal KPI panel updated on a fixed schedule (monthly): governance execution, reliability, market access, security assurance delta, and adoption/throughput.

This is where Terra Classic historically fails: plans appear, but accountability surfaces don’t harden. Outcome A is only acceptable if the accountability surface hardens.

A3) What a credible 90-day launch looks like (A is a delivery test, not a strategy test)

If you want this fork to be falsifiable, the 3-month window should contain deliverables that are “too real to fake”:

Day 0–30

• Publish plan v1.0 with owners + budgets + KPIs.

• Publish recovery operating system (board + cadence + comms).

• Ship 1–2 “credibility patches” (things that reduce institutional risk, not just tech debt).

Day 31–60

• Demonstrate governance execution: at least one workstream funded with milestone-based release gating.

• Publish first KPI report + first incident/retro template (even if “no incidents”).

Day 61–90

• Deliver at least one measurable outcome that affects investor risk perception (e.g., market-access continuity playbook, endpoint resilience improvement, governance participation intervention).

Investor rule: if the plan cannot produce non-trivial proof within 90 days, it will not produce a turnaround within 24 months.

12.2.4 Outcome B — Admission of incapacity + operator recruitment (professionalization)

Outcome B is not a defeat. It’s a credibility reset.

B1) Why Outcome B is rational (given the data)

The data already supports a simple claim: Terra Classic governance is optimized for voting outcomes, not for operating outcomes. High rejection rates, low median delegators, and thin voter participation indicate that the governance layer does not naturally convert attention into coordinated execution.

Meanwhile, the forum layer shows high ideation throughput (many topics, proposals, frameworks, and “recovery” narratives), but ideation alone doesn’t generate delivery. The Agora topic export shows 103 topics captured in that snapshot, including items explicitly about governance observability and even a “Master Recovery Roadmap” topic—evidence that “roadmap discussion” exists, but does not automatically become executable institutional machinery.

Outcome B acknowledges the truth most investors already price in: without professional operators, recovery claims are not investable.

B2) “Recruitment anchors” (documented) — what must be published immediately

Outcome B is acceptable only if it is paired with a structured operator recruitment process that is itself auditable:

1. Operator mandate (public):

   • scope, authority boundaries, reporting cadence,

   • decision rights vs governance votes,

   • performance metrics and termination conditions.

2. Procurement model (public):

   • RFP or equivalent process,

   • evaluation criteria,

   • conflict-of-interest policy,

   • budget ceiling + milestone disbursement rules.

3. Selection criteria (investor-grade):

   • verifiable case studies,

   • references and accountable leadership,

   • capacity evidence (team, delivery system, security posture),

   • willingness to operate under transparency.

4. Contract structure (even if simplified):

   • milestone-based payment,

   • clawback for non-delivery where feasible,

   • explicit deliverable acceptance criteria.

5. Transparency artifacts:

   • weekly operator updates,

   • monthly KPI updates,

   • incident reporting standard.

Investor translation: Outcome B must not be “we can’t do it” followed by silence. It must be “we can’t do it, therefore here is the hiring and accountability machine.”

B3) The “operator model” that fits Terra Classic’s reality

Because on-chain governance is not a company board and validators are not necessarily operators, the recruitment design must accept one constraint:

• Validators remain the approval surface (they can vote).

• Operators must become the execution surface (they can deliver).

Outcome B therefore requires a clean separation:

• Governance sets: goals, budgets, constraints, KPIs.

• Operators execute: roadmap, delivery, comms, incident response, stakeholder management.

Without this separation, Terra Classic keeps repeating the same loop: vote → argument → partial ship → drift.

12.2.5 Probability of success (A vs B) — a sober, investor-facing assessment

This section is intentionally blunt, because Chapter 12 is being written for investors first.

12.2.5.1 Baseline reality: governance conversion is currently weak

Given:

• thin participation (~0.24% of active wallets voting),

• high rejection rates,

• and a long history of “discussed but not operationalized” recovery concepts visible in the forum stream,

…the default expectation is that Outcome A fails unless it is forced into a proof-first shape.

A: Validator-authored roadmap (probability: low-to-moderate unless proof-anchored)

• Without proof anchors: low probability of producing investable recovery.
  Reason: the historical failure mode is not lack of ideas—it’s lack of accountable execution and hardened control-plane ownership.

• With proof anchors + hard reporting cadence + milestone-gated budget: moderate probability of producing credible progress.

Outcome A becomes plausible only if validators accept a new operating discipline: roadmap as contract, not roadmap as narrative.

B: Hire operators (probability: moderate if structured; low if political)

Outcome B can outperform Outcome A because it changes the unit of execution from “validator collective” to “accountable operator.”

However, it still fails if:

• operator authority is ambiguous,

• payments are not milestone-gated,

• political interference undermines delivery,

• governance cannot commit to letting professionals run the machine.

If B is done properly—mandate + procurement + accountability + KPIs—its success probability is meaningfully higher than “validator collective writes a plan and hopes execution follows.”

Investor rule: B is the higher-upside path if Terra Classic can enforce operator accountability and protect execution from governance thrash.

12.2.6 The decision test (how investors should evaluate what happens next)

Whether Terra Classic chooses A or B, investors should evaluate one thing:

Does the chain convert “attention” into “execution” within 90 days?

You can formalize this as an investor checklist:

• Is there a single accountable execution surface?

• Are deliverables milestone-gated with acceptance criteria?

• Is reporting periodic, standardized, and public?

• Do KPIs move in the same direction as the claims?

• Is the security assurance gap explicitly addressed (even if only as a staged plan)?

If the answer is “no,” the market will continue to treat Terra Classic as:

• a high-volatility attention asset,

• with weak institutional underwriting,

• regardless of how many proposals, threads, or narratives appear.

12.2.7 Implementation note (how this article connects to the rest of Chapter 12)

This fork is not “the roadmap.” It’s the gate that determines whether a roadmap is even plausible.

• 12.1 defines the principles: evidence-bound, accountability-first, KPI-driven.

• 12.2 defines the fork: A (validators become professional operators) or B (validators hire them).

• 12.3+ should define measurement as the investor interface—because “recovery” must become falsifiable, month by month.