Rust Capability and Ownership Manifest¶
This manifest records the current AGT Rust capability surface, the repository that owns each gap, and the evidence needed to change a status. It is a source-backed inventory, not a certification, compliance statement, or production-readiness claim.
The evidence baseline is AGT commit 7d0cef5, agent-hooks commit 8a06c9d, and ACS commit 6d71fe9. Recheck source, tests, trackers, and upstream specifications before updating a row.
Evidence rules¶
Allowed states: shipped, partial, missing, blocked, and deferred.
| Status | Required evidence |
|---|---|
shipped | The complete capability in the row's stated scope exists on current main. The row links an applicable normative artifact, or says N/A with a reason, and links implementation plus a behavioral test or official conformance vector. A public type, example, or documentation page alone is insufficient. |
partial | A useful implemented subset exists, but a named workflow, enforcement boundary, packaging path, or evidence requirement is incomplete. The row links the existing evidence, the limitation, and a tracker. |
missing | No current Rust implementation satisfies the capability. The row names one owning repository and a tracker. |
blocked | The intended work cannot complete until a named external decision or prerequisite is resolved. The row links the blocker and tracker. |
deferred | The capability is intentionally unscheduled pending a named ownership, demand, or sequencing decision. The row gives one present owner for that decision and a tracker. |
Every row has exactly one current owner. Contract changes to agent context, verdicts, approval, composition, interception records, or the CTK belong in responsibleai/agent-hooks. Changes to ACS manifests, evaluation, dispatchers, effects, or interceptor semantics belong in responsibleai/agent-control-spec. AGT owns its CLI, audit, replay, compliance, dashboards, SRE workflows, and AGT integrations. An AGT integration may consume canonical contracts; it must not fork them.
Source precedence¶
Use the first applicable source in this order:
- normative specifications and machine-readable schemas;
- official conformance vectors and reports;
- the canonical Rust implementation and its behavioral tests;
- AGT integration source and behavioral tests; and
- Python only as a UX or workflow exemplar when the higher-precedence sources are silent.
The canonical host contract is AGENT-HOOKS-0.1, with its schemas and CTK vectors. The canonical policy-interceptor contract is the ACS specification and manifest schema, with its runtime coverage and agent-hooks report.
Current and proposed architecture¶
AGT main depends on the published agent-control-spec 0.4.0-alpha.3 runtime and the agent-hooks host contract; the embedded ACS 0.3.1-beta engine was removed in PR #3939 (the continuation of #3561). policy-engine/docs/acs-retarget.md records what moved, the remaining upstream gaps, and the registry ownership decision that superseded the responsibleai/agent-control-spec#24 precondition. The agentmesh operator CLI still evaluates the crate's local rule-based PolicyEngine; it does not establish an AGENT-HOOKS-0.1 host-conformance claim, and depending on the published engine is not by itself such a claim either.
Rust capability inventory¶
Core, operator, and SRE capabilities¶
| Capability | Status | Owner | Canonical contract or exemplar | Current implementation and evidence | Limitation and tracker |
|---|---|---|---|---|---|
Core agentmesh governance primitives | partial | microsoft/agent-governance-toolkit | N/A for AGT-owned identity, trust, audit, MCP, rings, and lifecycle primitives; ACS applies where an AGT 5 policy interceptor is claimed | agentmesh modules and behavioral tests | Implemented primitives do not by themselves establish workflow, host-conformance, or operational parity. Trackers: #3680, #3083, #3084, #2986, and #3521. |
| Published ACS 0.4 and agent-hooks adoption in AGT | partial | microsoft/agent-governance-toolkit | Canonical ACS specification, schema, coverage, and agent-hooks CTK report linked above | Main depends on agent-control-spec 0.4.0-alpha.3 through policy-engine/sdk/rust; acs-retarget.md records the symbol mapping, the removed manifest fields and the upstream gaps | Dependency, not conformance: no AGT host harness or CTK report exists (next row). Upstream gaps #20 to #23 and the team-owner item ACS #24 remain open. |
Unified Rust agt operator CLI | partial | microsoft/agent-governance-toolkit | N/A -- AGT-specific operator UX; the Python CLI is workflow prior art only | Feature-gated command surface, dispatcher, and CLI tests cover check, policy, audit, and trust | Missing doctor, replay, offline integrity verification, compliance/OWASP verification, and dashboard workflows. Track #3680; initial CLI delivery was #2445. |
Local-rule agt check and agt policy commands | shipped | microsoft/agent-governance-toolkit | N/A -- these commands document the existing AGT-local PolicyEngine scope and make no ACS claim | check.rs, policy.rs, and behavioral CLI tests | Complete only for the documented local-rule surface. ACS alignment remains conditional on #3561 and is not implied by this row. |
agt audit tail and agt audit export | partial | microsoft/agent-governance-toolkit | N/A -- AGT-specific operator transport UX | audit.rs and behavioral CLI tests | Reads and re-emits serialized logs but does not verify the hash chain or embedded control records. Track #3680. |
agt trust show and agt trust set | shipped | microsoft/agent-governance-toolkit | N/A -- AGT-specific file-backed trust-store UX | trust.rs and behavioral CLI tests | Complete for the documented file-backed score workflow; this is not an external identity or authorization protocol claim. |
| Deterministic replay workflow | missing | microsoft/agent-governance-toolkit | N/A -- AGT/SRE workflow; Python replay is UX and workflow prior art only | No Rust replay command or bounded replay envelope exists on current main | Define a host-owned envelope over canonical records before implementation. Track #3680. |
agt doctor, policy linting, compliance and OWASP verification | missing | microsoft/agent-governance-toolkit | Agent-hooks CTK and ACS conformance artifacts are authoritative for their scopes; Python compliance CLI is presentation prior art only | No Rust doctor, verify, or lint-policy command exists on current main | Must distinguish conformance evidence from certification and bind any attestation to verified inputs. Track #3680. |
| Dashboard and broad governance observability | partial | microsoft/agent-governance-toolkit | OpenTelemetry specification; agent-hooks is explicitly a control plane, not a telemetry plane | Opt-in agentmesh policy spans have behavioral tests; the policy-engine workspace also has an OTel metrics bridge | Current Rust coverage is narrower than fleet dashboards and broad policy/trust/audit/prompt/MCP telemetry. Track #3680; telemetry foundation history is #2446. |
Host contract and existing integrations¶
| Capability | Status | Owner | Canonical contract or exemplar | Current implementation and evidence | Limitation and tracker |
|---|---|---|---|---|---|
| AGT Rust host adapter and CTK conformance claim | missing | microsoft/agent-governance-toolkit | AGENT-HOOKS-0.1, schemas, CTK vectors, harness contract, and claim rules | The canonical Rust SDK and CTK exist upstream, but AGT has no production-path harness or accepted per-part report | Package presence is not host conformance, and conformance is not security certification. Track #3680. Contract or CTK changes belong in responsibleai/agent-hooks. |
| Rig tool integration | partial | microsoft/agent-governance-toolkit | ACS host obligations over the published engine; the ACS and agent-hooks stack linked above | Real rig-core adapter and behavioral tests exercise allow, deny, transform, approval, bypass, and concurrency cases | Existing workspace crate is publish = false and builds on agent-control-spec 0.4.0-alpha.3 through the AGT host SDK. Do not duplicate it; track packaging and canonical-stack decisions in #3680. |
| Official MCP Rust SDK integration | partial | microsoft/agent-governance-toolkit | Official rmcp SDK plus ACS host obligations over the published engine | Real rmcp adapter and behavioral tests exercise pre- and post-tool enforcement | Existing workspace crate is publish = false and builds on agent-control-spec 0.4.0-alpha.3 through the AGT host SDK. It is distinct from, and must not duplicate, canonical agentmesh-mcp. Track #3680. |
| OpenAI Rust tool integration | partial | microsoft/agent-governance-toolkit | ACS host obligations over the published engine; OpenAI client types are transport integration, not policy semantics | Real async-openai adapter and behavioral tests exercise allow and pre-/post-tool denial | Existing workspace crate is publish = false and builds on agent-control-spec 0.4.0-alpha.3 through the AGT host SDK. Do not create a competing adapter; track packaging and canonical-stack decisions in #3680. |
| OpenTelemetry integration | partial | microsoft/agent-governance-toolkit | OpenTelemetry specification; ACS defines only redaction-safe telemetry semantics for its runtime | Existing agentmesh span sink has behavioral tests; the policy-engine metrics bridge and example also exist | The ACS bridge has no crate-local behavioral test, and neither path provides the broader dashboard surface. Extend existing signals rather than inventing another telemetry contract. Track #3680. |
| Goose/ACP host integration | deferred | microsoft/agent-governance-toolkit | AGENT-HOOKS-0.1 host contract and official CTK; ACS may be installed only as one interceptor | No AGT Goose/ACP production-path adapter or CTK report exists | AGT owns the decision on accepting a reference integration. If maintainers decline, implementation should move to the consuming Goose repository without changing canonical semantics. Track #3680; do not implement before ownership is agreed. |
Updating this manifest¶
Before changing a row:
- search open and closed issues and pull requests in all three owning repositories;
- inspect the current default branches, applicable specifications, schemas, vectors, implementation, and tests;
- keep exactly one owner and link a limitation plus tracker for every incomplete state;
- require implementation plus behavioral or official conformance evidence before using
shipped; and - update the package matrix and Rust README when operator-visible status or discoverability changes.