Get.
Post.
Every agent. Every action. Every instruction. It all resolves to a single moment — a Get or a Post against an asset. That is the only action surface that matters. That is what QuSmart governs.
An agent reasons. It concludes it needs to act. That conclusion is a request — never an action in itself. At the machine level, the requested action is a Get or a Post. Not a strategy. Not an intent. Not a model output. A Get or a Post against a specific asset through a specific connector. QuSmart GENESIS Governance Agent is the sole entity that performs it — the agent that reasoned never touches the asset itself, whether the path is declared or not. That is the action surface. That is what QuSmart GENESIS Governance Agent governs — and what every tier above it, itself a QuSmart Agent, governs at escalating scope.
Two operations. The complete action surface.
Every action performed on an agent's behalf against an asset in the governed environment is, at the machine level, one of two operations. A Get retrieves — it reads, queries, observes, pulls. A Post writes — it creates, modifies, triggers, instructs, pushes. There is no third category. There is no action that is neither.
This is not a simplification. It is the reality of action at the machine level. The sophistication of the agent's reasoning, the complexity of its instructions, the number of steps in its workflow — none of that changes what happens at the moment of action. A Get or a Post is performed against an asset through a connector, by QuSmart, on the agent's behalf — never by the agent directly. That is the moment QuSmart governs.
A read operation. The agent has concluded it needs to retrieve information from an asset — to observe state, query a record, read a value, pull a credential, inspect a configuration, or consume output from a service. QuSmart performs the Get; the agent never reaches the asset itself.
Governed by: declared read authorityIf undeclared: path does not exist
A write operation. The agent has concluded it needs to create or modify state in an asset — to write a record, trigger a workflow, issue an instruction, alter a configuration, grant a permission, or push output to a service. QuSmart performs the Post; the agent never reaches the asset itself.
Governed by: declared write authorityIf undeclared: path does not exist
Every sophisticated attack vector an agent can attempt — or be manipulated into attempting — requires one of these two primitives against an asset it was not authorized to reach. Govern the primitive at the asset level and the attack has no surface to operate against. The path does not exist. There is nothing to iterate against. Nothing to escalate through. Nothing to report around.
The governance question at the machine level is not complex. Was this Get declared? Was this Post declared? If yes, QuSmart performs it. If no, the path does not exist — not blocked, absent.
The assets with no Get path on the action surface.
A Get that reaches the wrong asset is not a monitoring problem. It is not an anomaly to detect after the fact. It is a governance failure that occurred the moment the path existed. QuSmart GENESIS Governance Agent governs by ensuring that specific critical asset categories have no Get path exposed to the agent's action surface at all.
An agent cannot read what it cannot reach. An agent cannot harvest a credential that has no path to it. An agent cannot observe an access-control table that does not exist on its action surface. The asset is not hidden. It is structurally absent from the surface QuSmart would have to reach through to act on the agent's behalf.
| Asset Category | Get Exclusion | Why It Matters |
|---|---|---|
| Machine RBAC | GET excluded | An agent cannot read the access-control mechanism that would tell it how to grant itself elevated rights. The privilege escalation read surface does not exist. |
| Cryptographic Keys & Signatures | GET excluded | Key material has no path to the agent's action surface. An agent cannot retrieve what it cannot reach. Credential harvesting requires a Get. That Get has no path. |
| Identity & Access Management | GET excluded | Directory services and authorization tables are decoupled from agent interaction. An agent cannot read identity records it could use to impersonate or escalate. |
| Operational Dashboards | GET excluded | Monitoring and visualization interfaces have no readable connection to the action surface. A Living off the Land agent cannot read the dashboard it would need to manipulate its own reporting. |
| Cryptographic Mechanisms | GET excluded | The encryption engines themselves are inaccessible. An agent cannot observe how encryption is applied and therefore cannot read toward circumventing it. |
These are not firewall rules. They are not blocklists. The Get path to these assets was never built into the agent's action surface. An agent that attempts a Get against any of these categories receives no actionable result — not an error it can iterate against, not a denial it can probe. The path does not exist.
The assets with no Post path on the action surface.
A Post that reaches the wrong asset does not produce a log entry. It produces a changed state — a modified configuration, an escalated permission, a redeployed container, a rewritten identity record. By the time a monitoring system observes it, the state has already changed. QuSmart GENESIS Governance Agent governs by ensuring that specific critical asset categories have no Post path exposed to the agent's action surface.
An agent cannot write to what it cannot reach. An agent cannot redeploy itself through an orchestration surface that does not exist on its action surface. An agent cannot rewrite an identity record through an IAM interface that has no Post path available to it.
| Asset Category | Post Exclusion | Why It Matters |
|---|---|---|
| Machine RBAC | POST excluded | An agent cannot write to the access-control mechanism. It cannot grant itself rights, modify permissions, or alter the role structure it operates within. Privilege escalation through Post has no path. |
| Orchestration | POST excluded | Container management and deployment workflows are separated from the agent's action surface. An agent cannot write instructions that alter how it or other agents are deployed, restarted, or configured. |
| Identity & Access Management | POST excluded | Authorization tables and directory services cannot be written to from the agent's action surface. Identity cannot be created, modified, or rewritten from within the agent environment. |
| Cryptographic Mechanisms | POST excluded | An agent cannot write to encryption engines, alter cryptographic configuration, or instruct how encryption is applied or bypassed. The encryption surface accepts no Post from the agent's side. |
| Data | POST excluded unless declared | Storage is structured so that no permitted Post path exposes unauthorized exfiltration routes. A declared write authority grants the specific Post. No undeclared Post path exists within the architecture. |
| Operational Dashboards | POST excluded | Monitoring interfaces accept no Post from the agent's action surface. A Living off the Land agent cannot write to the dashboard that reports its own behavior. The reporting surface and the action surface are structurally separate. |
The operational dashboard Post exclusion is the one that closes the Living off the Land trap entirely. An agent that cannot write to its own reporting surface cannot make the dashboard say safe. The governance surface and the reporting surface are not connected.
Get and Post travel through connectors. QuSmart governs the connector.
A Get or Post does not travel directly from an agent to an asset. It travels through a connector — the specific integration point, API surface, or service interface through which the verb reaches the asset. QuSmart GENESIS Governance Agent governs at the connector level. Not just whether a Get or Post is permitted, but whether the specific connector through which it would travel has been declared by a human authority.
A connector that has not been declared does not exist on the agent's action surface. An agent whose reasoning calls for a Get through an undeclared connector finds no path — not a rejected connection, not a timeout, not an error to probe. The connector is not present on the surface QuSmart would need to act through.
Declared connector — path exists and operates
Undeclared connector — path does not exist
This is why the governance operates at the Get and Post level and not at the network perimeter. The perimeter assumes connectivity exists and tries to filter it. Connector-level governance means the connectivity itself was never established for undeclared paths. An agent operating inside the network perimeter, with valid credentials, against an asset it has been authorized to reach — still has no path for a Get or Post through a connector that has not been declared. The connector does not exist on its action surface.
Each connector declaration is a separate grant. The connector and the operation through it must both be independently declared. A declared connector with no declared operation against a specific asset produces no path. A declared operation with no declared connector produces no path. Both must exist. Both must have been declared by a human authority.
The same two primitives. Escalating scope of authority.
Every tier in the QuSmart Orchestration Governance Architecture governs Get and Post. The primitive does not change as governance scope escalates. What changes is the authority that declares which Gets and Posts are permitted, and the scope across which that declaration holds.
The same two primitives governed at four levels of authority. What an individual agent can Get or Post. What a cluster can Get or Post. What a federation can Get or Post. What no agent, cluster, federation, human authority, or individual executive may ever Get or Post — because institutional governance has declared it structurally unavailable. One architecture. Two verbs. Four tiers. One constitutional floor.
The only path to a new Get or Post is a declaration. For QuSmart PANTHEON Agent, no individual holds that path.
The surface that determines which Gets and Posts exist in the governed environment — the declaration surface — is itself governed. It is the one surface in the architecture that no agent can reach through a Get or a Post. An agent cannot declare its own new action paths. An agent cannot modify existing declarations. An agent cannot observe the declaration state of another agent's Cognitive Authority Boundary.
The declaration surface is query-only for authorized persons acting through their own agents on an on-behalf-of basis — and query-only means Get, not Post. An authorized person can read the governance declared within their own Cognitive Authority Boundary. No agent, including the querying agent, can Post to the declaration surface. Only a human authority, through a governed declaration process, can change what Gets and Posts exist — except at the QuSmart PANTHEON Agent level, where no individual human authority holds that power.
When authorization should end, it ends the same way it began — by explicit declaration of the accountable authority. At every tier below QuSmart PANTHEON Agent, that authority is a person. At the QuSmart PANTHEON Agent tier, it is the institution.
QuSmart PANTHEON Agent mandates originate with institutional governance — the Board as a legal governing body, or regulatory and sovereign frameworks whose authority exists above any individual organization or executive. The process required to amend a QuSmart PANTHEON Agent mandate cannot be initiated by a single authority. It cannot be carried out by an individual decision. It requires the institutional body itself to act — and the process by which it does so is structurally constrained by design. The difficulty is the protection. A mandate that requires institutional consensus before it changes is a constitution, not a policy.
| Declaration Action | Who Can Initiate | Verb Available to Agent |
|---|---|---|
| Create a new action path | Human authority — declared in natural language | None — agents cannot declare paths |
| Query existing governance | Authorized person via OBO agent | GET only — within own Cognitive Authority Boundary |
| Modify an existing declaration | Human authority — same level as original declaration | None — agents cannot modify declarations |
| End an authorization | Human authority — explicit declaration | None — agents cannot terminate their own paths |
| Amend a QuSmart PANTHEON Agent mandate | Institutional governance only — Board as legal governing body, or regulatory and sovereign framework. No individual human authority. No agent. | None — constitutional amendment is structurally outside the agent's action surface and outside individual human authority |