digital-hygiene

digital-hygiene

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.

Review digital hygiene across accounts, devices, backups, domains, 2FA, privacy, and abandoned services. The goal is practical risk reduction, not security theater.

Trigger

Use when the user asks to:

• review accounts, backups, devices, passwords, 2FA, domains, or privacy settings
• track abandoned services or cleanup candidates
• prepare a safe digital cleanup checklist
• plan backup verification or device retirement
• decide what needs a reminder, task, vault update, or runtime config change

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/digital-hygiene/data.json when the user/runtime policy allows it.

Source decision

Store the source choice in $LIFEOS_DATA_DIR/digital-hygiene/data.json when useful:

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

This JSON shape belongs in $LIFEOS_DATA_DIR/<skill-name>/data.json, not global config.json. Use Life OS as the source of truth only for Life-OS-specific preferences, technical state, or notes explicitly created inside Life OS. Do not silently create a second private database when the runtime or an external system already owns the real data.