Eagle Ops
← Eagle AI
Course Standards

Druids Glen · Druids Heath

Not configured yet

1 · Pick a baseline template

Pre-fills every axis with the ideal values + acceptable bands typical of this venue type (USGA / GCSAA / GS3 reference). You then adjust the ideal or the acceptable band per axis below.

2 · Ideal state — your words

Describe what "ideal" means for THIS course. Free-form. The team reads this; the LLM uses it as context.

3 · What does ideal look like — per axis

Imagine a NOC with thousands of cameras / sensors / scouts running silently. Per axis you describe: what's ideal, and how far from ideal is still acceptable. Anything outside the acceptable band shows up as a deviation in the feed — you never browse raw readings. "Escalate past" is an optional hard line that bumps urgency.

Pick a template above to populate axes.

4 · Per-zone attention + spot annotations

Two controls per zone. Tier sets a permanent weighting (signature greens get escalated severity automatically). Annotateopens a satellite mini-map of just that zone — you drop a pin on the actual problem area, tag it, and we suggest fixes you can stamp into today's plan.

  • T1 signature: severity bumped up. "Watch" → "problem", "problem" → "urgent".
  • T2 standard: axis defaults apply unchanged.
  • T3 low attention: severity bumped down.
  • Untagged — treated as T2.

5 · Demo seed

Populate fixtures so the greenkeeper walkthrough has something to react to. Both seeders are idempotent — safe to click again.

Deviations feed

~7 realistic deviations across greens, fairways and resources.

Open feed →
Today's plan (live)

~12 tasks for today across Whiteboard / Brief / Corrective sources, mid-shift state with one in-flight.

Open Today →
Exemplar day · 2026-04-20

The hand-curated reference day for the client walkthrough. 20 tasks, every one DONE with realistic ±2–8min variances, full operator/equipment assignment + body/crew text. Same data renders in Whiteboard, Brief, and Today.