I'm starting to introduce the idea of an Octree that knows it's getting in bound "viewed" content. Previously the Octree would live in the server (no inbound content) or the client (inbound content)... and simply knowing where you were would be enough to know if you had inbound content.

But now, we're going to allow Octree's to live in network nodes that aren't servers or clients... the first example is the Assignment-client/Agent where it has a local Particle Octree. It's not a viewer (yet, maybe never) but it is also not an authoritative server.

So it might have locally created particles (from a script) and then it will get updates (from the server) when the local particle gets an assigned ID... but it's not actually a viewer. Knowing this allows us to optimize other work items. More below.