Documentation

AI Assistant Documentation

Use AccountHouse AI features with appropriate verification, privacy, permission, and financial-advice boundaries.

Audience: Household members using natural-language assistance and generated explanations. · 4-page PDF · v6.26.1

Logo header · watermark · generation date · multi-page

How to read this document

Sections move from purpose → concepts → calculation process → worked examples → edge cases. Formula boxes use plain mathematical notation for clarity; they are conceptual summaries, not API contracts.

  • Point lists call out operator-visible behaviour.
  • Callouts mark warnings, limitations, or important qualifications.
  • Worked examples use round numbers so you can reproduce the arithmetic by hand.

Purpose

The AI Assistant helps explain and navigate permitted AccountHouse information. Generated output can be incomplete or wrong and must be verified. When InteliHouse is enabled for your account, you get the fuller assistant surface with consent controls; otherwise a simpler chat may still be available.

  • Ask questions in natural language
  • Summarize permitted records
  • Get navigation or organizational help
  • Verify before acting

Data and permissions

The assistant should operate within the authenticated user's available context and permissions. It does not gain authority merely because a user asks for restricted data.

Usable context concept

Permitted product context + user prompt − restricted data

Verify generated output

  • Open source records.
  • Recalculate important amounts.
  • Confirm dates, filters, and currency.
  • Do not treat citations or confident language as proof.
  • Correct source data rather than relying on a conversational memory.

Financial boundary

Not professional advice

AI output is not financial, investment, tax, legal, credit, or accounting advice. Forecast explanations remain informational scenarios.

Prompt privacy

  • Do not enter passwords, API keys, card credentials, or unnecessary identity data.
  • Assume prompts can become part of operational records under applicable policy.
  • Avoid requesting data about people outside your permitted scope.

Actions and confirmation

Where the assistant can prepare or propose changes, review the exact records, amounts, dates, and scope before confirmation.

Check an answer

  1. Ask for the selected period and filters.
  2. Open the source report.
  3. Compare the contributing rows.
  4. Correct any mismatch before acting.

The ledger remains the source of truth.

When output is uncertain

  • Narrow the request.
  • Provide non-sensitive context.
  • Ask for assumptions.
  • Use deterministic reports.
  • Contact official support for account-specific issues.

Privacy, advice limits, and what we do not publish

AccountHouse is a household tracking and organisation tool. It is not a bank, payment processor, tax advisor, or investment advisor. Forecasts, health scores, balances, and alerts are informational.

  • Household data is scoped to your household; other families cannot see your ledger.
  • Public documentation explains product behaviour and calculation concepts, not proprietary internals.
  • Exact scoring weights, anomaly thresholds, cryptography parameters beyond high-level algorithms, and operational detection rules are reserved.
  • Generated content may hallucinate, omit context, or become outdated; never use it as sole support for a consequential decision.

Intellectual property boundary

This document describes what AccountHouse calculates and which inputs matter. It does not disclose source algorithms, secret constants, or implementation details sufficient to reconstruct proprietary systems.