Utilities

In plain words: Homestead: energy and water

Designed 4 min read 4 glossary terms 6 connected pages
The short version written for the Snayu team

How Homestead observes and balances energy, water, fuel and network resources, and handles environment requests from Keeper or Cultivator within commissioned device limits.

Why read it: Read when working on solar and battery logic, water control, or device actuation.
  1. 1Local battery, inverter, pump and fire vetoes always win.
  2. 2LychD sends typed requests, never prompt-made shell or relay commands.
  3. 3The home must stay safe without internet, model or cloud.

Words on this page, decoded click one for its card

The original text Underlined words open their plain-English card.

Before spending the afternoon's solar surplus, the household must know what remains reserved for the night. Utilities makes energy, water, gas or stored fuel, network, and device systems separately inspectable. It can observe, advise, or request an effect inside a commissioned envelope.

Map and observe

homestead.map_site@1 creates HomesteadPlan@1 from the dwelling, water points, circuits, critical loads, generation, storage, fuel/service boundaries, network zones, devices, work zones, hazards, unknowns, and professional or permit needs. homestead.observe_cycle@1 checks the attribution, calibration, age, and contradictions in bounded telemetry and weather before updating a ledger or showing a gap.

A device report, calibrated derivation, and reconciled estimate are different evidence stages. Energy, water, fuel, habitat, network, camera, and embodied-node ledgers keep their own truth. Observations, calibration, forecasts, plans, alerts, approvals, commands, receipts, laboratory evidence, professional documents, and configuration retain independent revisions. Gas and fuel remain observe-or-advise only: this contract supplies no burner, combustion, or valve-control PatternWorkflow.

Balance without bypass

homestead.balance_energy@1 uses critical-load policy with PV, load, battery, grid, alarm, and forecast evidence. Its advice or exact set-point intent stays inside inverter, BMS, anti-islanding, thermal, fire, and electrician-set protection. Model/GPU work is an ordinary household load. A finite surplus window may inform compute admission, but cannot schedule a model job, grant peer authority, or outrank refrigeration, habitat, communications, water, safety, or the declared battery reserve.

homestead.guard_water@1 works from well, tank, pressure, quality, weather, and allocation evidence. Pump or valve intent remains inside dry-run, pressure, level, freeze, contamination, and reserve interlocks. Sensor readings cannot establish potability.

The freshest local BMS, inverter, pump, float, pressure, and fire veto wins. Each effect binds asset/controller identity, configuration generation, commissioned envelope, live observations, preconditions, expiry, local reservation, expected postcondition, and compensation or containment. LychD sends typed requests; it does not emit prompt-produced shell, bus, GPIO, relay, or manufacturer commands.

Meet an environment request

A greenhouse needs water while an animal enclosure shares the same reserve. homestead.apply_environment@1 receives an exact KeeperEnvironmentNeed@1 or CultivatorEnvironmentNeed@1, or a reviewed household requirement, and proposes or admits one bounded environmental action. The care owner supplies suitability and source-reviewed needs. Homestead checks physical feasibility and its commissioned limits.

Before admitting the action, account for everyone it could affect. The site envelope must enumerate other affected occupants and their current admitted constraints, including shared water or energy consumers. Admission binds the exact need and originating owner, subject/placement/profile revisions, asset and controller generations, affected zones, units and bounds, resource ceiling, live evidence, validity window, and expected technical postcondition.

Unknown occupancy, expired requirements, conflicting bounds, or insufficient reserves yields a blocker or refusal. Arrival order and model preference cannot decide whose needs to discard. Return any feasible alternative to the affected owners for review.

After the attempt, HomesteadEnvironmentResult@1 records the requirement and admission identities, action/attempt id, reserved and observed resource quantities, controller receipt and independent observations, technical result, and unresolved effects. Its outcome distinguishes a proposal, refusal, verified completion, partial completion, interruption, and unknown effect.

The receiving care owner then assesses what that technical evidence establishes for its subject. A command acknowledgement alone cannot prove the measured postcondition, and reaching a set-point cannot establish a biological care verdict.

For a Legion body, the request carries only the fenced task, zone, resources, expiry, and stop conditions. Fresh body admission and local emergency control remain decisive. Lost acknowledgement blocks blind repetition until controller state, reservations, and effect evidence reconcile; cancellation cannot reverse already delivered water or heat. Ongoing environmental protection belongs to the commissioned local controller, even when ana InvocationJob Request or network connection ends.

Keeper and Cultivator can use human observations and work without Homestead. Exact settled requirements and result references do not grant access to either owner's database. Live multi-owner initiation, waiting, cancellation, or recovery needs the separately admitted Suite contract.

Follow the sun without moving the Lich

Beyond the household utility contract, a separately admitted coordination profile may offer delay-tolerant labor to a sovereign A2A peer from fresh evidence of surplus PV, battery margin, and compatible compute. The offer is coarse, expiring, and bounded by energy, time, task class, and local policy. Raw household telemetry need not travel. The destination rechecks load, forecast, thermals, reservations, and safety margin; no remote scheduler can override its local veto.

Only bounded labor and admitted artifacts cross. Identity, private GraphStep Map, memory, household records, and infrastructure authority remain with the LichAssistant. Context and Security separately admit egress. Price cannot widen those limits, and an unmeasured remote route cannot claim to be greener. Homestead supplies the energy evidence; the coordination profile must separately establish work admission, remote settlement, and recovery.

Return to observed state

The household must remain safe without internet, Wi-Fi, Master, model, or cloud. Lost acknowledgement leaves a physical effect unknown until the exact controller and independent sensors reconcile it. Restore keeps admission closed while clocks, controller generations, envelopes, pending effects, alarms, and local state are checked. Replacement devices and changed calibration add evidence instead of rewriting history.

Return to Homestead.