Where we fit
Access control is the gate. The substrate is the record.
As enterprises deploy AI agents into production, governance tooling has emerged across several distinct layers. Most address a single question: is this agent authorized to act?
§ 01 The layers
What you are likely evaluating.
Each layer serves a defined operational role, and enterprise architectures frequently require all of them.
Access & identity
Decides whether an agent is permitted to act: authorization, credentials, machine and agent identity. Necessary work.
Posture & monitoring
Discovers your agents and tracks telemetry in real time. Useful for operations.
Compliance attestation
Attests that your program and controls align with a standard. That documents governance policies.
Memory & recall
Gives your agents memory that persists across sessions: captures what an agent learns and surfaces context later. High value for operational continuity.
§ 02 Where Subnet345 sits
The record layer, by construction.
Maintain the access controls and monitoring systems already in place; they determine whether an agent is permitted to act. The substrate records and attributes instrumented actions by construction, operating from emitted telemetry rather than post-hoc reconstruction.
The gate and the record represent distinct operational mandates. A comprehensive governance architecture requires both. Plexus adds gates of its own: a policy can block a message at the boundary, and a budget scope can refuse further sends once it is over its threshold. Both are off until you set them, and every refusal is recorded.
Access controls determine whether an agent may act. Plexus produces the tamper-evident record of its actions.