Keystone is built in two parts on purpose: a domain-agnostic Core that's true of any department, and domain editions that supply the vocabulary, ceremonies, and rubrics. Keystone SRE is the first — because that's where the constraint bites hardest and where we have unfair depth.
Frameworks change orgs when checklists can't, because a framework survives contact with turnover, reorgs, and quarter-end. Scrum outlived every team that adopted it. EOS runs thousands of companies without its author in the room. That durability comes from being named, versioned, opinionated, and installable — properties a best-practices doc doesn't have. Keystone ships all four: v1.0, with defined ceremonies, required artifacts, and explicit exit criteria for “installed.”
Seven components, none of which mention SRE — that's the design test.
Operational and project work are planned, tracked, and reported separately, with an explicit per-team ops-capacity budget as a policy knob. Within two weeks, every team can answer “how much of your capacity went to keeping the lights on?”
Every recurring operational task is classified Eliminate / Automate / Optimize / Retain. The Automate queue is a ranked backlog — frequency × time × risk × automatability — feeding the automation engine. Findings become a work queue, not a report.
Four metric classes that normalize across teams and tools: outcome, work-health, delivery, and adoption. Editions supply definitions; the classes never change — so a VP can read any team's scorecard the same way.
One dataset, four renderings: team weekly view, manager rollup, director monthly, VP/board quarterly narrative. Teams stop writing status decks; executives stop reading fiction.
Generic ceremony shapes — weekly ops review, triage session, monthly org review, quarterly exec briefing — each with agenda, inputs, outputs, timebox, and owner. Editions add domain ceremonies into these slots.
Who owns policy, who can halt work, who triages, and the explicit contract between the function and the rest of the org — embedded, consulting, platform, or hybrid.
Levels 0–4 per pillar. One instrument, three uses: the assessment, the roadmap generator, and the progress report. You are re-scored against the same rubric that diagnosed you — no consultant grade inflation.
The SRE domain pack: eight pillars, each shipping a teaching module, artifacts, ceremonies, metric definitions, and a maturity rubric.
Objectives that gate decisions, not decorate dashboards. Artifacts: service catalog, error-budget policy. Ceremony: error-budget review.
The ledger, the register, the triage cycle. The pillar that feeds the automation engine.
Sustainable load, clear command, honest severity. Artifact: on-call health report.
Blameless in practice, not just in the template. Ceremony: incident review.
Because most incidents are self-inflicted. Ceremony: production readiness review.
Ahead of the growth curve instead of underneath it.
Instrumentation standards that make the metrics abstraction real rather than aspirational.
The policy layer: who decides, who reports, what escalates.
Metric definitions — SLO attainment, error-budget burn, incident frequency and severity, MTTR, toil %, on-call load, the DORA keys — are specified abstractly: what, why, and how to derive from common tooling. The edition is tool-agnostic. The platform is the reference implementation, not a requirement.
Every pillar is scored 0–4 against the same behavioral rubric — first by the assessment, then by every progress report after it.
Heroics and ad-hoc reaction. Operational work is invisible and infinite, and the same incidents recur.
The work is becoming visible. First owners and measurements exist, but the cadence is still fragile.
Roles and ceremonies are named and scheduled. Artifacts exist but adherence is inconsistent.
The system self-runs: ceremonies happen without prodding, scorecards stay current, decisions cite the data.
The pillar improves itself — freed capacity funds the next round of elimination, and the metrics prove it upward.
The Core/edition split isn't packaging — it's architecture. The same chassis that runs an SRE org runs a support desk or a finance-ops team, because work separation, triage, and altitude reporting are true of any operational function. Future editions — platform engineering, security engineering, data/ML ops, and beyond engineering entirely — ship as edition packs on the same Core. Today, one edition is active: Keystone SRE. We prove it completely before we extend it.
Three doors, in ascending commitment.
Free, 7 minutes, instant scored report across the pillars.
The written spec of the framework — join the waitlist.
We install it with you — assess, blueprint, install, operate, graduate.