finance-checkup

finance-checkup

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 personal finance coordination signals without becoming a bank, tax system, or password vault. The goal is to surface anomalies, recurring costs, renewal pressure, and useful next actions.

Trigger

Use when the user asks to:

• review spending signals, subscriptions, recurring bills, savings goals, or renewals
• check for unusual charges or upcoming payments
• prepare a money decision or budget review
• track financial documents and deadlines
• decide whether a finance item belongs in tasks, calendar, docs, or an external finance tool

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

Source decision

Store the source choice in $LIFEOS_DATA_DIR/finance-checkup/data.json when useful:

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