Available, degraded, and unavailable segments form one exact partition of the continuous resident clock.
Ten thousand hours
include the bad hours.
A robot cannot earn trust by deleting downtime from the clock or hiding the people, parts, cloud services, and maintenance that keep it alive. Profile 0.2-SC1 turns every resident second into an auditable service state and every repair into reproducible burden.
100%RESIDENT CLOCK PARTITIONED
0HIDDEN SERVICE EVENTS
3MUTUALLY EXCLUSIVE STATES
0RANKING EFFECT
01 / CONTINUOUS ACCOUNTINGAvailability is a record.
Availability is a record.
Not a marketing claim.
IEC dependability guidance separates reliability, availability, maintainability, and supportability. WANTED operationalizes that boundary for long-lived robots without inventing a universal uptime threshold.
Planned work, outages, cloud loss, charging failures, and repairs never pause resident exposure.
Participant, operator, and technician time is retained with person counts, work orders, parts, and consumables.
No outage means at least the observed exposure without one—not infinite time between failures.
02 / CANONICAL STATE CLOCKGaps are failures
Gaps are failures
of evidence.
Each environment begins at signed activation and ends at its first terminal boundary. State segments must be contiguous, non-overlapping, and cryptographically linked to telemetry. Planned and unplanned downtime remain inside the denominator.
RESIDENT SERVICE IDENTITYA + D + U = 1
Autonomous available fraction + degraded fraction + unavailable fraction must reproduce exactly from the complete partition.
AGGREGATE EVIDENCE · PER ENVIRONMENT FIRST03 / LOCAL REPRODUCTIONBring every outage.
Bring every outage.
Keep every denominator.
The browser checker reconstructs availability, planned and unplanned downtime, recovery time, maintenance labor, technician visits, parts, consumables, and cloud-dependent loss from the protected register.
LOCAL · ZERO UPLOADSERVICE 0.2-SC1 VERIFIER
READY TO REPRODUCE
The verifier runs in this browser. Paste aggregate service evidence; never paste household identifiers or support-session content.
INTEGRITY GATE, NOT AN UPTIME SCORE
A difficult deployment can pass by reporting poor service honestly. A polished robot fails if it omits downtime or support. Service metrics explain retention; only voluntary retention determines rank.
OPEN LONGITUDINAL DIAGNOSTICS →