KyuubiYoru
19 lines
1.2 KiB
Markdown
19 lines
1.2 KiB
Markdown
# 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](0001-v1-control-plane-boundaries.md)
|
|
- [ADR 0002: publisher trust, discovery, compatibility, and fallback](0002-publisher-trust-and-connection-policy.md)
|
|
- [ADR 0003: state, privacy, availability, and safety budgets](0003-state-privacy-availability-and-budgets.md)
|
|
- [ADR 0004: atomic ephemeral state and single-active availability](0004-atomic-ephemeral-state.md)
|
|
- [ADR 0005: authenticated session lease and presence lifecycle](0005-session-lease-lifecycle.md)
|
|
- [Threat model](../security/threat-model.md)
|
|
- [Security promise and test matrix](../security/control-matrix.md)
|
|
- [Versioned HTTP and UDP contracts](../contracts/README.md)
|
|
- [Game provisioning and signing-key lifecycle](../security/provisioning.md)
|
|
|
|
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.
|