Source binding and live verification
Let a member choose the right automatic source, prove that it is live, and route it without creating fake practice history.
A connector can discover several sources. A package can accept several observation contracts. Neither fact identifies which source should control one member's Practice Mode.
The host owns a source binding that joins:
- Station and connector installation;
- discovered source identity;
- exact observation contract;
- Pursuit and Practice Mode configuration;
- member-granted input route;
- verification and health state.
Setup flow
Discover
Station displays sources reported by the reviewed connector using safe labels and health. The package listing explains why the source is useful.
Select
The member chooses a source for the ready Practice Mode. The host checks exact contract compatibility and required connector grants.
Verify live input
The member performs one harmless recognizable action. Station observes and validates it through a verification route that cannot commit an Attempt, Measurement, progression, Story Event, or Sprint evidence.
Bind
After explicit confirmation, the host creates a revocable route. Future live Runs may use it, but merely binding a source does not begin practice.
Monitor
The player and Station show healthy, stale, reconnecting, unavailable, or revoked state. Manual fallback remains available when the package supports it.
Why verification is not practice
Testing a dart throw, timer split, or browser move during setup should not create a fake personal best, history row, rank change, or creator moment. Verification is host-owned source proof with a separate route and retention policy.
Revocation
Removing a binding prevents new routes immediately. Revoking the connector grant also closes the underlying source. Previously committed Attempts retain their provenance without preserving live connector authority.