Enablements

Business capabilities, scored with receipts.

Name what the business needs to be true — new hires productive on day one, backups that restore on time, checkout that holds at peak. Panaptico scores each capability from its requirements and shows exactly where every point went.

Enablement · Business continuity

Not enabled

Backups Restore Within the Recovery Window

Every tier-1 database can be restored to a clean environment inside its four-hour recovery window.

35%

Not enabled

83% confidence

Requirements

2 of 7 healthy

3 failed · 2 unknown

Coverage

85%

of weight backed by decisive evidence

Evaluation

Every 15 minutes

stale after 60 minutes

Owner

Platform Engineering

with Database Reliability

How 100 became 35

Full weight100
A restore was tested in the last 30 days−30
Backups replicate to a second region−10
Snapshots are kept for 14 days−10
Standby capacity fits production load−10
Restore runbook reviewed this quarter−5
Health score35
Every point on the score is accounted for

1 required check failing

No restore test in 41 days makes the capability Not enabled — no averaging it away.

2 unknowns cost points

Scoring

A score you can take apart.
Every point accounted for.

A capability's health is never a black box. It's built from requirements you choose, weighed by evidence you can open.

  1. 1

    Requirements

    Each capability is built from weighted requirements: the policies, monitors, workflow verifications, and datasets you already trust.

  2. 2

    Required checks

    Mark the requirements that can't fail. If one does, the capability is Not enabled — no averaging it away.

  3. 3

    Confidence

    Confidence shows how much of the weight is backed by decisive evidence right now, so a high score on thin evidence looks thin.

  4. 4

    State

    Health and confidence roll up to one state, re-evaluated on a schedule and kept with its full history.

Enabled

Requirements are healthy and backed by current evidence.

At risk

Still working, but trending toward failure or leaning on thin evidence.

Degraded

Working with real gaps — points lost to failing or stale requirements.

Not enabled

A required check failed. The business can't count on this capability.

Unknown

Not enough decisive evidence to call it either way.

Dependencies

See what it depends on.
And what each gap costs.

Open any capability to see every requirement, where its evidence comes from, and how many points it holds or has lost.

Enablement · Dependencies

New Hires Are Productive on Day One

Degraded · 58

Health

58

of 100 weight

Confidence

81%

weight with decisive evidence

Requirements

5

1 required

Owner

IT

Employee IT workspace

RequirementSourceLatestWeightLost

A new hire can sign in and reach their apps

Required

Workflow verificationPassed 1d ago300

Every new hire has a managed laptop

Policy2 of 14 violating25−25

Account provisioning failures

MonitorClear180

Core app licenses have headroom

PolicyEvidence 3h stale17−17

HR roster start dates are current

DatasetSynced 1h ago100

If the required verification fails, the capability is Not enabled — whatever the score.

A capability is the sum of its evidence

−25

2 new hires have no managed laptop yet

Stale evidence costs points

Examples

Capabilities teams track.
Written the way the business asks.

New hires are productive on day one
Backups restore within the recovery window
Checkout stays fast at peak load
Customer email always delivers
Leavers lose access the same day
Laptops stay managed and patched
Month-end jobs finish on time
Every production service has an owner
Certificates renew before they expire

Start with one capability.
See what it really depends on.

Pick the outcome the business asks about most. Panaptico shows what it depends on and where it stands today.