6 sample lanes
Habitat, water, invasive, timber, access impact, and opportunity review are all visible.
Conservation & Land Health
This page turns stewardship planning into a practical workflow: which habitat priorities deserve attention, where erosion or water concerns may matter, which invasive-species questions stay on watch, and how future land-care opportunities can be compared without exposing real field details.
Sample workflow only. No official assessments, coordinates, route details, contractor records, or location-specific land data are included.
Habitat, water, invasive, timber, access impact, and opportunity review are all visible.
The workflow keeps urgency obvious before any real site detail is added.
Outside review stays visible where land-impact risk is higher.
This PR keeps the stewardship view metadata-only and safe.
This page should help the owner compare stewardship concerns and next steps without turning the app into a source of truth for coordinates, access instructions, or official land assessments.
Future Supabase path: start with sample `conservation_notes` rows that only contain titles, statuses, urgency, and next actions.
This preserves the same privacy guardrail used across visits, maps, and documents.
The first backend connection can stay read-only while still making the page feel useful.
Habitat priorities, erosion and water concerns, invasive placeholders, timber stewardship notes, trail-impact questions, conservation opportunities, and next actions.
The first backend-linked conservation rows should be sample titles, categories, urgency, seasonality, review needs, and next actions only.
Start with read-only `conservation_notes` metadata before any richer field-note workflow exists.
A useful land-health workflow does not need coordinates, routes, access instructions, or contractor details to support owner review.
Protect the privacy boundary even if later PRs connect sample notes to Supabase.
Higher-risk lanes should stay grounded in conservation and land-health review rather than drifting into operational detail.
Use review gates and next actions before turning these lanes into larger planning systems.
No real coordinates, access notes, routes, contractor details, official assessments, parcel records, or private landowner records are included.