Published route entries from the Route Manager projection.
Current page: About GardenPlanner. Canonical solution inventory for routes, API commands, public references, Dataverse records, and architecture evidence. Primary task: Read the canonical route, API, reference, and schema inventory for the solution. Use the main page controls and local actions for the next likely steps.
Release certification is pending
Navigation and public projections are available; the final receipt will be installed after route UAT completes.
Solution About
One source of truth for the current GardenPlanner experience
This page inventories the current routes, API commands, Dataverse reference records, and schema evidence that support the public experience, the Map Explorer, inventory, and scenario-safe simulation.OpenAPI-aligned command descriptors available to people, automation, API clients, and agents.
Reconciled runtime inventory.
Governed external source records from Dataverse.
Enabled foreign-attribute contracts that describe how outside evidence can be read or cached.
Operating status
Service availability
This view reads the certified release’s immutable receipt; it does not launch diagnostics while the page loads.
Certified release
unavailable
No exact release receipt is available.
Executable inventory
Public executable-surface subset
This public view excludes internal and diagnostic surfaces. Readiness separately requires the full release inventory to be reconciled.
- Posture
- drift
- Version
- 0.2.0
- Status
- failed
- Surfaces
- 15
- Findings
- 0
- Inventory hash
sha256:8493a10cbbad2f4b2252309cd987591c96f4ab1570d1f2093b8a593c36569158- Source inventory
sha256:dc05549c4effc0c2c890e7708d355eb56bd34674ef5f395a7bd8b9a9c7a98d76- Source manifest
sha256:277d6f1388bbe9abdc4c2e56536f01c3ea7c3b9714e41f1d2bf96d5c9b9da5c5- Telemetry binding
- unavailable
- Binding fingerprint
Route inventory
Current pages come from one route catalog
Map Explorer owns live plot discovery, governed overlays, and Zone Construction proposals. Accepted simulation belongs to Player Season and PEM through the canonical Crops and Cash player.
Featured projectionGuardrails
How this page stays honest
- The page renders projections; it does not mutate operational records.
- User-facing copy is resolved from the Dataverse page-content projection with en-CA and fr-CA parity.
- Visible command claims are backed by Route Manager and OpenAPI routes.
- Obsolete prototypes are hidden, archived, or redirected toward current surfaces.
- Scenario outputs remain review evidence until an approved operational workflow promotes them.
OpenAPI
The About page reads the same command surface agents use
Route Manager exposes route, command, and surface projections so UX, UIA, API clients, NPC agents, and documentation can stay aligned.
Featured projectionRead the 200 ha Dataverse playing-field area precision objective: fields as fields, forest/riparian breaks as forest, drainage as stream, and woody edges as edges.
Discover every read-only Crops and Cash simulation, map, imagery, replay, and evidence capability.
Compatibility route for the old five-field corn benchmark. New clients should use crops.cash.production-zone-benchmark.read and the generic production-zone projection.
Read the competitive Green River five-plot challenge, replay timeline, win state, placement assessment, 3D garden overlays, and universal map references.
Render a self-contained Azure Maps imagery SVG with the validated Dataverse GIS winning overlay, or a diagnostic fallback background when the tile service is unavailable.
Read the winning garden boundary, five target plot polygons, actual 3D garden footprints, planted content, reality layers, and topography evidence as WGS84 GeoJSON.
Read plot placement scores, reality-layer natural fit, actual garden footprint acreage, WGS84 envelopes, centroid evidence, and 3D tree/root/shadow overlay dimensions.
Stage harvest markers for projected picking, packing, shared-economy allocation, and order-manifest readiness.
Read bilingual farm and garden inventory classes, common products, and deterministic affinity rules for zone, inventory, crop, animal, mineral, and soil interactions.
Stage inventory-management markers for planned inputs, tools, stock, harvest bins, storage, and scenario-only inventory allocation moves.
Stage maintenance-task markers for watering, pruning, mulching, scouting, soil building, path repair, and seasonal stewardship moves.
Evaluate multiple isolated NPC agent submissions against the same Green River rules, map geometry, and negotiation action set.
Public interfaces
Inspect the live local contracts
Dataverse registry
Public sources are records, not loose page text
External APIs, imagery, GIS, weather, crop, hardiness, and public-context references should be registered in Dataverse before they are presented as solution evidence.
Seaton’s growth changes the surrounding human and ecological context in which any Green River proposal would need to operate.
The Rouge establishes an adjacent conservation and public-land context that makes habitat continuity, water, and responsible interpretation central concerns.
The decision not to use the Pickering Lands for a future airport changes the planning context, but it does not by itself determine a new land use.
The 1972 expropriation continues to shape questions of tenure, displacement, public memory, and who participates in future land decisions.
Land Over Landings connects decades of civic advocacy to present questions about agriculture, conservation, and accountable land-use decisions.
Holding federal hearings in Brougham placed affected communities inside the public record; their testimony remains relevant to future consultation.
The 2015 and 2017 transfers show one realized consequence of a different land future: former airport lands became protected agricultural and ecological landscape.
This source lets the reader verify a connected claim and understand its authority, scope, and limits.
Foreign attributes
How outside evidence enters local projections
ERM
The schema links place, map, inventory, simulation, evidence, and review
The updated ERM remains generated from the Dataverse Schema Factory. The About page summarizes the main capability lanes and links them to the current schema posture.
Sites, teams, players, contacts, public zones, Indigenous priorities, and civic context define who can speak for a place.
Spatial nodes, features, overlays, topology, validation evidence, and geometry versions keep map work reviewable.
Inventory classes, items, assignments, acquisitions, care tasks, and manifests support real and scenario-safe operations.
Planning scenarios, turns, commands, logs, scoring, economy assumptions, and replay frames model possible futures without overwriting reality.
Knowledge sources, public references, external source records, foreign attributes, citations, and licensing notes keep claims traceable.
Drafts, review packets, approvals, audit posture, and separation of duty govern what can become current operational truth.