kenlck Review operability
Assess one repository, a repository group, or an existing fleet evidence bundle. Judge whether operators can detect, diagnose, control, and recover the running software.
Run the lens
- Read the standalone lens protocol completely and prepare the supplied scope with lens ID
operability. - Read the operability checks completely. Apply every check family relevant to the deployment model, criticality, exposure, and interaction edges.
- Trace operational signals from production behavior to diagnosis and response. Classify supported outcomes as strengths or findings; record unavailable telemetry backends, platform controls, and operational artifacts as unknowns.
- Follow the protocol to account for every contract-registered check family, validate the result, ingest it, and hand back the canonical artifact path.
For raw collection, read and follow the safety model. Review supplied telemetry and operational artifacts; treat unsupplied live-system state as unknown rather than probing a deployment.
Boundary
Own production visibility, diagnostics, deployment control, and operator guidance. Route correctness under failure to software reliability and measured capacity or resource cost to performance efficiency.
Completion
Complete when: every in-scope repository has an exact commit or explicit unavailable state, every applicable check family is accounted for, every claim has bounded sanitized evidence at an appropriate confidence, gaps remain visible in unknowns and coverage, and the shared result validator succeeds.