Why types matter

Each document is uploaded with a linked_item_type that tells Frank what kind of document it is. Beyond the standard types (insurance policy, asset, liability, income, transaction, statement), Frank now has canonical types for the financial / legal documents people actually keep:

| Type | Use it for | |---|---| | trust_deed | SMSF trust deed, family trust deed | | building_contract | Construction / KDR / dual-occ contract | | qs_depreciation_report | Quantity surveyor Div 40/43 schedule | | mortgage_variation | Rate change letter, IO→P&I notice | | partnership_agreement | Business partnership / shareholders agreement | | will | Current will | | power_of_attorney | EPOA / POA | | binding_death_nomination | Super BDBN | | super_pds | Super fund PDS / member statement | | rental_lease | Current tenancy lease | | investment_pds | ETF / managed fund PDS | | company_constitution | Corporate beneficiary constitution | | amendment_deed | Variation deed for trust / SMSF | | tax_document | Generic tax-season uploads (PAYG summary, rental statements, investment income) |

What the type unlocks

1. Auto-RAG embedding — these types are auto-chunked + embedded into a per-user vector index after OCR completes. That means Frank can answer questions like "what does my trust deed say about distributions to minor beneficiaries?" with semantic search across the actual document content, not just substring grep.

2. Type-aware filtering — Frank's search_user_documents tool accepts a doc_type filter, so you can scope queries: "find the milestone schedule in my building contract" stays inside building_contract docs.

3. Tax-doc sharing — tax_document uploads (and any document explicitly toggled "share with practice") become readable by your practice. Other types stay private unless you opt in per-document.

How to upload

Drop the PDF / image into any feature-matching surface (e.g. attach a building contract from the construction-tracking panel, attach a trust deed from the SMSF page). The right type is pre-selected. For ad-hoc uploads, use the Documents panel and pick the type from the dropdown.

Privacy

Documents are stored encrypted at rest in Supabase Storage. Per-user RLS ensures you're the only one who can read them — except where you've explicitly toggled practice_visible = true or used the tax_document type, which extends read access to a practice you've accepted an invitation from.