What needs to be done
Define the high-level architecture of the new Connect protocol: session model (does the app need a new session? what triggers one?), session lifetime, and the other structural decisions that determine how CoreApp and Connect are wired together. This is scoped to the shape of the protocol, not the final message definitions — those are expected to change, including a possible move to Hashbuffers before production.
Why it is needed
The architecture has to be built around the session/lifetime model now, because getting this wrong means rearchitecting later. Individual messages changing later is expected and cheap; the general shape changing later is not. A working prototype needs this decided so implementation can start against a stable architecture even while message details are still moving.
Acceptance criteria
What needs to be done
Define the high-level architecture of the new Connect protocol: session model (does the app need a new session? what triggers one?), session lifetime, and the other structural decisions that determine how CoreApp and Connect are wired together. This is scoped to the shape of the protocol, not the final message definitions — those are expected to change, including a possible move to Hashbuffers before production.
Why it is needed
The architecture has to be built around the session/lifetime model now, because getting this wrong means rearchitecting later. Individual messages changing later is expected and cheap; the general shape changing later is not. A working prototype needs this decided so implementation can start against a stable architecture even while message details are still moving.
Acceptance criteria