Maintenance

In plain words: Homestead: repairs and maintenance

Designed 2 min read 5 connected pages
The short version written for the Snayu team

How Homestead tracks a fault from first report through a bounded work order to verified closure, including parts sourcing and inspection cameras.

Why read it: Read when building fault tracking, work orders or inspection features.
  1. 1A work order names asset, tools, expiry, stop conditions and expected verification.
  2. 2Cameras need purpose, masks and retention; no face recognition by default.
  3. 3Silence never closes a fault; verification evidence does.
The original text Underlined words open their plain-English card.

An inspection reports a leak. Before anyone can close the work, the household needs an account of the fault, the work requested, and the evidence of its result. Homestead's maintenance design follows that account from the first report through verification.

homestead.maintain_site@1 can begin with an attributed alarm, inspection, runtime record, or calendar event. It may lead to containment advice, research, a bounded work order, verification, or an unresolved result.

Begin with the fault record

An uncertain cause may call for research or containment advice before a work order can be defined.

If the work needs a part, the requirement passes to Scavenger with the compatibility, certification, serviceability, environmental, budget, and evidence requirements that a candidate must meet. Scavenger returns dated evidence about candidates and sellers. Purchasing a candidate and commissioning it each require their own admission.

Define the work before acting

A work order identifies the asset and zone, the tools and resources, its expiry, and the conditions that require work to stop. It also says what verification is expected, so the result can be assessed against the work that was authorized. For the leak example, it could require a follow-up inspection of the same asset, with the findings reviewed before closure.

A human or droid works within that envelope. For controller-backed work, the local controller or emergency stop can refuse fresh work or halt work already underway, even after LychD admitted it. Human professional judgment remains with the responsible person. Design certification, construction, and hazardous repairs remain outside this contract. The Homestead contract gives the full exclusions, including permits, unsafe energization, interlock bypass, and general robot authority.

Admit an inspection channel for its purpose

A future Tether route could carry private inspection and exact approved controls. Principal identity and effect authorization would still be validated independently of network access. A public dashboard is never the fallback for that private route.

Where a camera is involved, its admission specifies the purpose, masks, active hours, viewers, and retention. Face recognition, neighbour surveillance, ambient audio, public streaming, and indefinite retention are absent by default. Sight may analyze an admitted feed; authority over the camera, site, maintenance work, and droid remains separately owned. An inspection view supplies evidence without extending the work order.

Verify the effect before closing the work

An alarm opens work; silence does not close it.

Use the verification named in the work order to assess the result. A lost acknowledgement after an action leaves its effect unknown, so recovery must inspect the controller, independent evidence, open work, and remaining hazards before repeating the action or declaring completion. If that evidence cannot establish the required result, keep the work unresolved.

Return to Homestead.