From Scope to State: A Working Model of QM

QM becomes easier to reason about when one work episode is followed from its people and room to its final state. This checkpoint connects the scope layers, turn-local context, scoped computer, memory, files, session, and harness into one causal chain. The practical judgment is simple: when a fact, file, process, permission, or transcript entry appears, the reader should be able to say who owns it, who can see it now, what survives later, and what changes when the audience or provider changes.

One work episode, seen through scope

Imagine a startup preparing a product launch. A product manager has personal notes from customer interviews. The product team has a shared project channel with its own history and working files. The organization has common instructions, approved tools, and an administrator who may need to govern the deployment. The team wants an agent to turn research into a launch plan, but it does not want every private note or personal login to become channel property.

The work begins with a request in the project channel. The channel, not the product manager's identity, is the target scope for that turn. QM can mount organization context read-only, use the channel workspace as the writable home, and apply any team context that the current kind of conversation permits. The actor still matters: they are the person initiating the turn, and their identity is part of the authorization calculation. But the full channel audience matters just as much because the reply will be delivered to the room.

Suppose the product manager deliberately shares one research document with the channel. The document enters the turn as a carried, read-only resource with an identifiable source. It does not turn the manager's entire personal workspace into a channel layer. The agent can use the document to draft the launch plan, but the resulting plan belongs to the channel's work unless the user deliberately sends or publishes it elsewhere. The scope boundary has not blocked collaboration; it has made the transfer specific.

The core then assembles a turn-local view. It brings together the current scope's writable context, authorized shared handles, relevant memory recall, visible skills, policy, and delivery choices. The model sees a projection of this arrangement, not a universal inventory of everything the initiating person could reach. If the manager leaves the project or the document's grant is revoked, the next turn can omit the source even though the channel session still exists. The durable conversation and the temporary view are related, but they are not the same object.

The agent now needs a computer. QM routes the channel's work to its scoped sandbox or to an explicitly authorized resource. Creating a computer would not have copied the manager's personal notes; selecting a default would not have changed a process already running elsewhere. The agent can write a draft into the channel workspace, run a bounded process, and publish an important deliverable independently of the computer's recovery window. If the team later opens the session through a different audience, the session projection may show less than the original turn saw.