Keep protocol handling outside the matching rules
Karthik brings experience with C++ network protocols and market connectivity. A natural next design step is to place a narrow network adapter in front of the matching engine, so byte streams and message framing do not shape the core order book.
That boundary can make partial reads, framing, validation, and disconnect handling explicit. If the chosen transport is a byte stream, the adapter must reconstruct complete messages from arbitrary read chunks. The transport and wire protocol are not selected yet; these are design questions for a later phase, not completed features.











