Rendezvous architecture decisions
These records define the v1 architecture baseline. A later change to a ratified decision requires a superseding ADR and corresponding contract/test updates.
- ADR 0001: v1 control-plane boundaries and domain
- ADR 0002: publisher trust, discovery, compatibility, and fallback
- ADR 0003: state, privacy, availability, and safety budgets
- ADR 0004: atomic ephemeral state and single-active availability
- ADR 0005: authenticated session lease and presence lifecycle
- ADR 0006: bounded compatible session browser
- ADR 0007: caller-owned .NET publisher and browser SDK
- ADR 0008: scoped join attempts and one-time connection tickets
- ADR 0009: authenticated bounded LiteNetLib NAT mediator
- ADR 0010: typed connection outcomes, deadlines, and caller-owned fallback
- Threat model
- Security promise and test matrix
- Versioned HTTP and UDP contracts
- Game provisioning and signing-key lifecycle
These decisions intentionally leave gameplay authority, player identity, simulation, persistence, social features, skill matchmaking, and gameplay traffic with each game. Relay is future evidence-driven scope, not part of v1.