Configuration
Here you define what gets watched, how the tenant treats file churn and deletion, and which on-prem agents may feed this cloud watcher — the governance surface for hybrid ingest.
Policies and watched folders update as you edit; field agents still use explicit actions. All of this is demo-only until the control plane is wired.
Display name (this watcher)
Nickname in the page title and my watcher menu. Stored in a browser cookie for this demo (not DynamoDB).
Clear the field and save to use the built-in default name again for watcher 42.
Delete & update policies
Stored per tenant; applied when sources change or disappear (spec §10). Choosing a value below posts immediately (demo stub). Production uses signed control messages (spec §7).
Watched sources
Analogous to WatchCommand::StartWatching — path, role, location hint, backup to staging. Edits post automatically (debounced while typing).
Field agents (on-prem)
Trusted agents already feeding this cloud watcher. New agents must be accepted before they are treated as providers.
Trusted (connected)
| Agent | Status | Last uplink | Notes |
|---|---|---|---|
field-agent-office-1 | connected | 2026-04-02T14:02:11Z | MQTT control + S3 MPU uplink; systemd on Linux. |
field-agent-lab-7 | connected | 2026-04-02T13:58:40Z | Feeds file:/// paths under lab ingest roots. |
field-agent-retail-west | degraded | 2026-04-01T09:12:00Z | High latency; uploads gated on Foundry ACK. |
Incoming connection requests
Agents on customer networks initiate pairing; you confirm identity, then accept below.
field-agent-manufacturing-eastEd25519 key fingerprint acme-mfg-2026… (mock)
field-agent-dr-datacenterPairing code ••••9821 expired in 15m (mock)
Connect a new field agent
Submit a pairing request name (mock). In production this would follow MQTT / console handshake.