Reliability-oriented automation
Automation that checks whether the commanded state was actually reached, retries what failed, and leaves a way back.
Identification
Established. Demonstrated by two or more published systems, so the pattern is repeated rather than singular.
Repeatable outcome
Automation that reports what actually happened rather than what it attempted.
The pattern is the same whichever system it appears in. An action is issued, the resulting state is read back from the thing itself rather than assumed from the absence of an error, and a mismatch is handled explicitly — by retrying, by stopping, or by restoring what was there before. Partial failure is a designed-for case rather than an unhandled one, and the operator can tell the difference between “done”, “did not run”, and “half done”.
That last distinction is the point. Automation that cannot report a partial result is automation whose output has to be checked by hand, which removes most of the reason for having it.
Scope and boundaries
This describes how the automation is built, not what it controls. The two systems that demonstrate it are a lighting integration and a document-maintenance tool; the shared property is the verify-and-recover structure, not the domain.
It does not imply:
- Continuous operation of someone else’s environment. Nothing here is a monitoring service, an on-call arrangement, or a managed deployment.
- A guaranteed recovery. A recovery path is designed and exercised; whether a specific failure in a specific environment is recoverable depends on that environment.
- Any availability commitment. Uptime, latency, and response figures are not claimed anywhere on this site, because none have been measured under a commitment.
The evidence is public source in both cases, so the claim can be checked rather than taken on trust.
Evidence systems
Published systems that demonstrate this capability, derived from those records rather than asserted here.
L3D-SYS-005
docmend
A document maintenance tool that separates scan, plan, apply, verify, and restore, defaults to a dry run, and can resume after interruption.
Open source under MIT, with published releases. Install it or read the source.
L3D-SYS-007
HA Light Controller
A Home Assistant integration that checks whether a light actually reached the commanded state and retries when it did not.
Open source under MIT, with published releases. Install it into a Home Assistant instance.
L3D-SYS-014
DFBU
A Linux desktop application for backing up and restoring configuration files, with mirror and archive modes, post-backup verification, and a safety backup before any restore.
Open source under MIT, with published AppImage releases. Download it or read the source.
Active offerings
None. This capability describes work that has been done, and nothing on this site is for sale today. If that changes it will appear on the availability page as a record with its own scope and exclusions.
Related records
The capability index lists the rest. What can actually be obtained today is on the availability page, which is a different question from what has been demonstrated.