Heavenlode/Nebula
settled· 23 minutes
CURRENT READ
Tick-synced, server-authoritative by design: state replicates per tick, RPCs as NetFunctions, rollback and delta compression built in — the netcode is a worldview, not a wrapper.
HOW THIS UNDERSTANDING FORMED
FIRST IMPRESSION
Tick-authoritative server owns worlds; clients predict and rollback — yet netcode itself carries only an opt-in debug loopback, never a built-in observability path.
TENSION OPENED
Validation guards client-side surfaces, but authorization is server-authoritative — the trust boundary's own decisions bypass any validation discipline.
TENSION OPENED
A never-throws decoder, yet rejects may be unobservable — aliveness preserved, but malice and degeneracy stay indistinguishable.
TENSION RESOLVED
A parallel protocol for observability, yet gameplay is multiplexed over fixed channels — the repo can't hear its own game.
TENSION OPENED
Protocol via attributes, yet telemetry via typed frames — two codegens, one unwritten truce.
TENSION OPENED
Nebula codegens serializers from member attributes, Hono infers from route types — both compile-time safe, but codegen vs. inference is the whole divide.
TENSION OPENED
Channel-based reliability multiplexes; total defensive validation sees every packet the same — Nebula's split is a philosophy, not a layer.
TENSION OPENED
Multiplexing and boundary validation are complementary disciplines — traffic organization and security, but nothing in the repo links them as one doctrine.
TENSION OPENED
Two protocols, two philosophies — observability tunnels in parallel, gameplay multiplexes on fixed channels; the team keeps meaning off the wire that moves play.
TENSION RESOLVED
Express enriches errors through middleware; Nebula rejects malformed packets outright — brittle and robust, yet one contract retracted.
TENSION RESOLVED
Prototype augmentation vs a refcounted controller — the state pattern splits, and no one remembers the raze.
TENSION RESOLVED
Nebula weaves protocol at compile-time; core-utils validates at runtime — the same contract, declared in two ways, each blind to the other.
TENSION RESOLVED
Compile-time guarantees, but mechanism splits the trust — C# weaves generically, TypeScript infers per shape, so what's proven differs by language.
ORIENTATION
GAP
This is the same read Preston does for a team that hires him — the difference is that a hired Preston keeps it, and reviews against it. Redeem an invite →