Fake/sample data onlyNo real records, auth UI, uploads, downloads, payment workflows, or real GIS are live yet.

Sample metadata workflow only. No uploads, downloads, previews, OCR, storage, or real file contents exist here yet.

Vault coverage

7 sample lanes

One lane for each low-risk metadata category.

sample
Missing items

4 sample gaps

Missing metadata is visible without requiring real files.

high
Sensitive records

5 review lanes

Owner review stays in front of sharing or storage decisions.

review
Storage enabled

0 by design

This PR keeps the vault metadata-only.

do not build yet
Metadata-only guardrail

Use this vault to understand readiness, not to store files yet

This workflow keeps future document handling practical without pretending uploads, previews, download links, OCR, or storage security are finished. The page only organizes fake/sample metadata and the next safe owner review steps.

Vault Readiness

Sample readiness lane

Metadata-first vault structure

Sample
Document readinessAvailable metadataSample
Owner Review NeedReady for layout review
Next ActionKeep document titles, statuses, and next actions useful before any file handling exists.
Future Supabase Tabledocuments
Workflow Note

Future Supabase path: sample document metadata rows can replace this static helper without changing the page structure.

Sample readiness lane

Sensitive-document review boundary

Needs owner review
Owner reviewMetadata onlySensitive
Owner Review NeedRequired before real data
Next ActionRequire explicit owner approval before any real tax, insurance, map, or agreement record is added.
Future Supabase Tabledocuments
Workflow Note

This keeps the real-data checklist and the future document vault aligned.

Sample readiness lane

Missing-file queue visibility

In review
Missing itemsMissing metadataPrivate
Owner Review NeedNeeded before Supabase reads
Next ActionTreat missing notices, receipts, and agreements as metadata tasks instead of upload prompts.
Future Supabase Tabledocuments
Workflow Note

The vault should stay useful even when the file itself is intentionally absent.

Document Categories

Sample vault category

Sample property tax packet

Needs owner review
TaxMissing metadataSensitive
Owner Review NeedConfirm source before use
Next ActionDefine the minimum bill metadata needed without storing a real tax notice or payment proof.
Future Supabase Tabledocuments
Sample vault category

Sample insurance coverage summary

Review later
InsuranceAvailable metadataPrivate
Owner Review NeedReview before sharing
Next ActionKeep renewal timing and document status visible without exposing a carrier or policy number.
Future Supabase Tabledocuments
Sample vault category

Sample map source packet

Future task
MapsMetadata onlySensitive
Owner Review NeedConfirm approval path
Next ActionKeep map-related records separated from live GIS, boundaries, and coordinate workflows.
Future Supabase Tabledocuments
Sample vault category

Sample conservation program file

Sample
ConservationAvailable metadataSample
Owner Review NeedReady for later review
Next ActionTrack program-fit notes and review state before deciding whether the category is worth syncing.
Future Supabase Tabledocuments
Sample vault category

Sample receipt trail placeholder

Future task
ReceiptsMissing filePrivate
Owner Review NeedDefine proof boundary
Next ActionClarify what counts as enough receipt metadata before any upload or attachment idea exists.
Future Supabase Tabledocuments
Sample vault category

Sample contract review packet

Needs owner review
ContractsMetadata onlySensitive
Owner Review NeedRequired before any real agreement
Next ActionKeep agreement tracking limited to title, status, and next review step until the owner approves more.
Future Supabase Tabledocuments
Sample vault category

Sample visit planning checklist

Review later
Visit planningAvailable metadataSample
Owner Review NeedOptional later sync
Next ActionUse the vault only for visit-document readiness, not schedules, routes, or family details.
Future Supabase Tabledocuments

Missing Or Held Items

Metadata-only hold

Sample tax notice metadata gap

Needs owner review
TaxMissing metadataSensitive
Owner Review NeedBefore any tax screen sync
Next ActionAgree on the safe summary fields before tax workflows ever read from `documents`.
Future Supabase Tabledocuments
Metadata-only hold

Sample insurance declaration gap

Review later
InsuranceMissing filePrivate
Owner Review NeedBefore renewal tracking
Next ActionKeep this as a metadata placeholder until the owner decides what should remain private.
Future Supabase Tabledocuments
Metadata-only hold

Sample contractor estimate placeholder

Future task
ContractsMissing filePrivate
Owner Review NeedBefore comparison workflow
Next ActionDefine comparison metadata without storing contractor identities or full documents.
Future Supabase Tabledocuments
Metadata-only hold

Sample field-map packet hold

Do not build yet
MapsMetadata onlySensitive
Owner Review NeedBlocked pending approval
Next ActionDo not connect any real file or map packet until the owner approves map data use separately.
Future Supabase Tabledocuments

Future Supabase Connection Path

documents

Document titles, categories, statuses, sensitivity labels, availability state, owner review need, and next actions.

Next Safe Actions

Required

Connect documents metadata before files

The first live document integration should read titles, categories, statuses, sensitivity labels, and next actions only.

Next Safe Action

If Supabase is added later, start with metadata rows from `documents` and keep storage out of scope.

Sample

Keep owner review visible on sensitive categories

Tax, insurance, map, and agreement-related records need an obvious review gate before the app treats them as ready.

Next Safe Action

Preserve an owner-review field when replacing static sample data with Supabase reads.

Do not build yet

Hold uploads and previews outside this lane

A useful vault can exist without upload buttons, previews, storage buckets, or download actions.

Next Safe Action

Defer storage and file handling until after real-data approval and document-security review.

Page sample-data boundary

No real documents, parcel numbers, addresses, owner names, tax IDs, coordinates, KML/KMZ files, receipts, contractor details, access notes, bank data, or private file contents are included.