AgentPlat Trust: eligibility filters without new authority

Trust answers a constrained eligibility question

The core concepts reference describes evidence as records of observations and decisions, while Trust profiles and filters narrow an existing local decision. That distinction prevents a positive assessment from becoming a universal permission token.

For an illustrative specialist-selection process, evidence may rule out a candidate for a particular role. A candidate that remains eligible still needs the normal assignment and effect controls. Eligibility is useful precisely because it has a scope.

Inspect the adapter boundary that applies the filter

The release-channel documentation identifies explicit server-side Trust integrations for Mesh and inference control. Calls routed through those opt-in paths receive their filtering or restriction behavior.

A direct provider, handler or dispatcher call outside that composition keeps its own behavior. Installing the Trust package is therefore not proof that every relevant invocation uses it. Review the actual call graph when deciding how broadly to describe the deployment's coverage.

Keep evidence uncertainty visible

The release reference describes scoped evidence lifecycle and policy-exact eligibility rather than a single unconstrained reputation score. Your integration should preserve why the selected evidence is applicable to the current decision.

If an assessor lacks the required inputs, do not silently substitute the most favorable previous outcome. Define how your selected policy handles missing or conflicting evidence and retain that result. A dashboard should distinguish a successful assessment from an assessment that was never performed.

Do not confuse Trust with a mandate

The Morphogenesis governance reference explicitly separates Trust and capability from a decision mandate. The same agent can be capable of a task without being authorized to approve its own organizational change.

Keep these facts separate in application records: the evidence used for eligibility, the current assignment and the exact decision or effect authorization. Combining them into one “trusted” badge obscures which boundary supplied permission.

Evaluate the integration at both allowed and denied paths

• Identify the configured Trust adapter and policy.
• Trace an eligible decision through that adapter.
• Supply evidence that the policy should restrict.
• Inspect behavior on a direct call outside the adapter.
• Confirm that a favorable profile cannot bypass an effect gate.

Use the maturity matrix and exact package documentation to select a version. These checks examine your composition; they do not establish a general safety score for an agent.