Installed
Migration, seed file, env template, and browser helper are already in the repo.
Dashboard
This homepage is a sample-only review surface for the real Farm Manager app: it points to the main planning boards, highlights owner-review priorities, and keeps future land-management work organized.
Local-first planning shell only. No real property, finance, tax, map, document, route, contractor, family, or private owner data is shown anywhere on this dashboard.
The new Property Overview workflow is the central summary for the app. Use it first to see the sample property profile, known gaps, map and document readiness, and how the planning lanes connect together.
Backend Readiness
This dashboard can try one narrow client-side Supabase read for approved sample command-center metadata while preserving static export and the local helper-module fallback. If env vars, session, or rows are missing, the page keeps working without blocking the owner.
Migration, seed file, env template, and browser helper are already in the repo.
The dashboard falls back to local command-center sample metadata until env vars are added.
Supabase env vars are not configured in this build, so the dashboard is using local sample command-center metadata.
PR #49 is merged, but it is an approval checklist, not permission to add real records.
Supabase env vars are not configured in this build, so the dashboard is using local sample command-center metadata.
This dashboard still builds without any Supabase environment variables.
The first optional backend lane only reads approved sample command-center metadata. No writes, uploads, auth UI, storage, or payments are added.
The merged approval checklist still prevents real property, tax, map, document, and access data from entering the app.
No live rows are required for this dashboard. When env vars or a signed-in development session are missing, the panel stays informative without blocking the page or removing sample-only safeguards.
Command center
Switch between blockers, readiness, and priorities to scan what is safe to review now, what is waiting, and where the next owner attention belongs.
Supabase env vars are not configured in this build, so the dashboard is using local sample command-center metadata.
Blocker view
This view keeps the current sample-only blockers in one place so the owner can filter by topic, compare severity, and jump straight to the workflow that needs the next review.
Showing the full cross-board blocker set so the owner can compare what is waiting across the dashboard.
Property summary should feel like the front door to the rest of the app.
Finance planning should stay useful without turning into a live payment console.
Revenue lanes should compare options without pushing the owner into premature outreach.
Stewardship work should stay privacy-safe while still guiding the next review.
Visit planning should stay practical without exposing real routes or schedules.
Document handling should remain metadata-only until real storage is approved.
Future Supabase path: blocker rows can later be derived from workflow status metadata layered on top of `properties`, `finance_entries`, `revenue_opportunities`, `conservation_notes`, `visit_tasks`, and `documents`.
Open tasks
Use the queue summary to see which follow-up lanes need attention now and jump into the full Open Tasks workflow when the owner wants the full action view.
Urgent work stays easy to spot without pretending anything is live or time-sensitive.
Dependencies and approval holds stay visible before the queue grows.
Owner-review lanes stay distinct from blocked or deferred work.
The queue prepares future work without storing any real owner or land details.
Decide the minimum summary fields that stay useful without exposing private owner or parcel details.
Higher-risk revenue concepts are still out of scope until simpler, land-safe ideas are easier to review.
Compare one stewardship-aligned income concept against one higher-upside concept using the current board language.
Draft a small sample label set for watch, monitor, review, and outside-input lanes.
Property overview, finance, maps, documents, visits, revenue, and conservation are ready for layout review.
The new sample-only property summary now ties the upgraded planning surfaces together in one place.
The local-first scaffold still avoids real bills, maps, documents, routes, family details, and private files.
The app now has a central sample summary, which makes a small future Supabase read easier to place without breaking the static shell.
Review the central sample property summary for profile, known gaps, land-use zones, workflow links, and next safe actions.
Review fake carrying costs, due-date placeholders, annual totals, and the safety note that the app does not make payments.
Review sample GIS planning questions, source boundaries, local-first map rules, and private-layer guardrails.
Review a sample metadata vault for categories, missing items, sensitivity, and next safe actions before any file storage exists.
Review a sample field-readiness workflow for checklist phases, weather placeholders, equipment, follow-ups, and safe next actions.
Review a sample opportunity workflow that balances revenue potential against effort, risk, land-health impact, seasonality, and readiness.
Review a sample stewardship workflow for habitat priorities, erosion watches, invasive placeholders, timber review, access impact, and next actions.
Point the owner toward the main planning boards and summarize what deserves attention next.
Pretend to be a real operations console with live records, reminders, uploads, or payment workflows.
Every count, amount, status, and recommendation on the dashboard remains fictional for safe owner review.
Review path: start with Property Overview, then confirm the dashboard points clearly to Finance & Taxes, Maps, Documents, Visit Planning, Revenue Opportunities, and Conservation & Land Health.
Use the blocker view to see what is actively waiting and which workflow should be opened next.
Switch to readiness view to confirm which boards feel ready for owner review versus later refinement.
Use the priority view to keep the next owner attention on the workflows that matter most right now.
All command-center views stay fake/sample only and are structured so a future read-only Supabase summary can slot in later.
This scaffold does not include real acreage, tax amounts, account numbers, parcel details, document files, royalty values, property notes, route details, family schedules, coordinates, KML/KMZ files, or private records.