Logo
Explore Help
Sign In
HeiKyu/Rendezvous
2
0
Fork 0
You've already forked Rendezvous
Code Issues 27 Pull Requests Actions Packages Projects Releases Wiki Activity
Files
codex/issue-25-test-client
Rendezvous/docs/architecture/README.md
T
KyuubiYoru 94aba8a3bb
quality-gate / quality (push) Successful in 59s
Details
feat(client): standardize connection outcomes (#13)
2026-07-16 10:18:41 +02:00

1.7 KiB
Raw Permalink Blame History

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.

Reference in New Issue View Git Blame Copy Permalink
Powered by Gitea Version: 1.26.4 Page: 346ms Template: 1ms
Auto
English
Bahasa Indonesia Deutsch English Español Français Gaeilge Italiano Latviešu Magyar nyelv Nederlands Polski Português de Portugal Português do Brasil Suomi Svenska Türkçe Čeština Ελληνικά Български Русский Українська فارسی മലയാളം 日本語 简体中文 繁體中文(台灣) 繁體中文(香港) 한국어
Licenses API