Station connectors
Chasing Mastery public platform
Health and recovery
Keep automatic evidence understandable through startup, stale sources, reconnect, duplicates, gaps, and restart.
Automatic input is only magical when failure is legible. A player should never quietly stop updating while implying that evidence is healthy.
Health states
| State | Meaning | Member presentation |
|---|---|---|
| starting | process/source opening | brief bounded preparation state |
| ready | source live and observations current | automatic input ready |
| degraded | usable with known limitation | explain limitation and fallback |
| reconnecting | source interrupted; retry in progress | retain last committed truth, show stale |
| failed | retry exhausted or configuration invalid | actionable recovery, manual fallback |
| revoked | authority removed | source stopped; reauthorization required |
Recovery requirements
- Backoff is bounded and observable.
- Reconnect does not mint new identity for replayed upstream events.
- Duplicate observations remain harmless.
- Sequence gaps become explicit diagnostics and creator evidence gaps.
- Station process restart can reconcile connector state and active routes.
- Package UI requests an authoritative snapshot on foreground/reconnect.
- Committed Attempts never depend on the connector remaining installed.
Exactly-once effect, not delivery fantasy
Networks and processes can deliver at least once. Stable observation identity, host deduplication, expected activity revision, and package determinism create an exactly-once authoritative effect for one event.
Diagnostics
Expose connector state, safe source label, last healthy timestamp, retry count, protocol errors, gap/dedup counters, and capability state. Keep raw sensitive payloads, tokens, file contents, and member identity out of ordinary logs and support exports.