Validated Patterns — runbook trust tiers

Runbooks carry a "Validated Pattern" trust tier — modeled on Red Hat's validatedpatterns.io — so you can tell a battle-tested playbook from an untried one at a glance. You'll see the badge on runbook cards and in the Runbook Library (Marketplace).

The three tiers:
• Sandbox (default) — community/unproven. Any new runbook starts here. The badge is quiet; treat the steps with discretion.
• Tested — EARNED, not asserted. A runbook becomes "Tested" the moment it's actually executed end to end with every required step passing. The badge records when it last passed and the environment (e.g. the OpenShift version) it ran on.
• Maintained — Turtini-validated. Turtini-authored library patterns that are proven across orgs and kept current. The top trust signal.

How a runbook earns "Tested":
You don't click a button — you run it. When you execute a runbook against an Environment (in the customer portal / lab runner) and the last required step passes, the runbook is automatically stamped as a validated pattern with that run's result. Re-running keeps it fresh.

Freshness / "Re-verify":
Like Red Hat's quarterly re-test model, a Tested runbook that hasn't had a fresh passing run in 90 days dims to a "Re-verify" badge. Run it again to clear the flag — it's a nudge that the steps may have drifted from reality.

For Turtini platform admins:
You can promote a runbook to the "Maintained" tier (or reset it) from the runbook card. Use it for vetted, Turtini-blessed library patterns like the OpenShift Service Mesh + mTLS workshop.