household-maintenance

household-maintenance

Mandatory integrity contract

Before acting, load and follow ../../references/data-integrity.md. Its provenance, missing-value, correction-history, defensive-write, backup, and recovery rules are mandatory for this subskill.

Track maintenance obligations for homes, vehicles, appliances, warranties, insurance, and recurring chores. The point is fewer forgotten filters, inspections, and expensive surprises.

Trigger

Use when the user asks to:

• track home, vehicle, appliance, or equipment maintenance
• plan repairs, inspections, warranty checks, or service visits
• review recurring household chores and seasonal tasks
• capture model numbers, warranty pointers, or service-provider notes
• decide what needs a reminder, task, calendar event, or document pointer

Operating model

1. Resolve the active runtime and private data directory.
2. Read $LIFEOS_DATA_DIR/config.json when available.
3. If source ownership for this domain is unknown, inspect runtime-owned systems read-only and propose a source decision before writing anything.
4. Load only runtimes/<active-runtime>.md if runtime-specific commands, storage pointers, delivery, scheduling, or integration behavior are needed.
5. Do not load other runtime adapters for the same task.
6. Prefer pointers, access notes, review dates, and short operational state over duplicated raw data.
7. Ask before changing external systems, creating reminders, contacting people, importing data, broad migrations, or destructive cleanup.
8. Record useful Life OS coordination state under $LIFEOS_DATA_DIR/household-maintenance/data.json when the user/runtime policy allows it.

Source decision

Store the source choice in $LIFEOS_DATA_DIR/household-maintenance/data.json when useful:

{
  "source_decisions": {
    "household_records": {
      "owner": "runtime|external|life-os",
      "runtime": "<active-runtime>",
      "source": "<tool-or-system>",
      "access": "<short pointer or retrieval instruction>"
    }
  }
}