Prepared builder example · October 12, 2026 · fictional records

One woodlot.
Five open projects.

A co-op wants to understand a proposed harvest, preserve its woodland connections, and keep field evidence and permission separate. Here is a small first-use story builders can inspect and improve.

farmOS

Record a dated activity.

GSIP

Observe soil; retain uncertainty.

VergeCommon

Coordinate, document and review.

DFM

Compare modeled landscape plans.

OpenTEAM

Clarify data rights and shared terms.

1. Start with an honest observation

obs-synthetic-001 is a fictional desk-exercise note. No soil sample, photograph or GSIP submission exists. Soil measurements, estimates and uncertainty are unavailable; they are not zero.

The same observation ID appears in the farmOS Activity CSV and VergeCommon field draft. Those files are manual handoffs, not live synchronization.

2. Compare a concrete planning choice

The local DFM engine evaluated these two synthetic plans. Switch the view to see the treatment that changes the modeled connection.

Dark green: core areas · light green: retained connection · grey: road · blue: crossing · orange: treatments. This drawing shows input geometry; it is not an analytical map of wildlife passage or a real parcel.

DFM tests modeled structure. A passing plan does not establish species movement, soil improvement, legal access or ecological viability. Soil estimates do not select harvest decisions in this example.

3. Keep review and permissions explicit

The VergeCommon note is a draft. Another steward must review any saved record. OpenTEAM's shared vocabulary helps distinguish permission to collect, access, export and publish.

At 12:30 UTC, the fictional publication grant is withdrawn. Future publication is denied. The steward's separate own-record export remains permitted. Live/backup erasure and prior-recipient reconciliation remain pending.

4. Give builders a useful next contribution

Build a small offline converter from a verified, privacy-safe observation format to a Verge field draft and farmOS Activity record. Preserve IDs, units, source versions and unknowns. Produce drafts; never silently approve or publish.

Existing: DFM–VergeCommon Landscape Package contract.
Proposed: GSIP/farmOS observation adapters and this end-to-end manual workflow.
Community review: OpenTEAM terminology; no endorsement or partnership claimed.

Open the walkthrough · Builder handoff · First-use experiment · Actual local calculation receipt

Published synthetic example. All geometry is fictional, copied from the MIT-licensed upstream DFM fixture. No telemetry, network requests, credentials or external actions. Source identities and credits: attribution and validation.