Intramedial is in restricted beta. At sign up or sign in, you have to provide the beta tester password you received or request one at preview@intramedial.com. Thank you.
Loading…
trust.getModule 15
Plane module
Trust scores and autonomy
Read an agent's trust score and the autonomy tier it has earned, so autonomy follows conduct the plane has actually seen.
trust.get returns an agent's trust profile: a score from 0 to 100, the number of observations behind it and when the last one landed. Released and abandoned leases, undeclared effects, ruling faults and rollbacks each move the score by a fixed amount, and time pulls it back toward 50.
Agents act when the plane says yes, and the record says why.
Put admission in front of your MCP servers, repositories, SaaS tools and cloud accounts. Every agent gets a lease or a reason – and you keep the lever to stop any of them.
Conflict frequency, policy violations and task completion are named by the product but have no safe definition yet, so they move no score. Read the score as lease hygiene, effect honesty, ruling faults and rollbacks only.
Record
The record
What gets recorded
profile
The agent's profile, or null when the plane holds none for that DID.
profile.score
The score from 0 to 100, decayed to the time of the read.
When the latest observation landed, in milliseconds.
tier
From trust/tier: observe, propose, act-with-review or act.
policy
From trust/policy: the point values, the decay and the tier floors, with the signals that are not scored.
Mechanism
Step by step
How it works
Every agent starts at 50
Enrolling an agent seeds its profile at 50 with no samples. Deprovisioning resets it to the same baseline.
Conduct moves the score
A release adds 0.5 and an abandoned lease takes 5. An undeclared effect takes 10, an over-claimed one 2, a ruling fault 8 and a rollback an operator had to make 15.
Time pulls it back
A score decays toward 50, halving the distance every 14 days. A high score settles down without fresh good behavior, and a low one recovers without fresh faults.
The tier is read from the score
trust/tier returns the highest tier whose floor the score clears: observe from 0, propose from 40, act-with-review from 65 and act from 85.
Before giving an agent more to do, an operator reads its score and how many samples stand behind it. Fifty with no samples is a stranger, not a good record.
A change train's gate
A change train reads the trust of the agents it has exposed to a change, and a missing profile holds the train rather than passing it.
A Gatehouse door
A door reads a counterparty's score and sample count. No profile is reported as none, never as a neutral 50.
Watching decay at work
An agent faulted a month ago reads closer to 50 than on the day of the fault, with no operator action.
When to use something else
Deciding one action. Admission checks grants, not the score; use coordination.admit for that.
Judging an agent's work. The score counts lease hygiene, honesty about effects and faults found by rulings; find collisions with detection.run.
Seeing which observation moved a score. The profile keeps a total and a sample count, not a list of observations.
Evidence
Guarantees
What it does, and what it does not
A module is a strong claim about a narrow thing. Rely on it for exactly what it is.
It does
The score comes from fixed point values and a 14-day half-life, so the same observations at the same time give the same number.
A profile is per workspace: what one workspace observes of a DID never moves another's score for it.
A deprovisioned agent's DID returns to the baseline, so a recycled DID starts clean.
It does not
That the score is deserved. Three signals have no safe definition yet and move nothing.
That rulings in an agent's favor raise its score. Only faults lower it; no signal rewards a win.
That the agent is safe to trust today. A high score decays toward 50 and says nothing about changes since.
Details
Build notes
Before you build
The starting tier
A score of 50 clears the propose floor of 40, so a new agent reads as propose, not observe.
Owner notice
When an observation moves an agent across a tier floor and the agent has an owner, the owner is notified, as a warning on a downgrade and as information on an upgrade.
Manual observations
trust/observe adds a signed number of points to a DID. It needs the policies.approve permission.
Limits and metering
did is required for get and tier. When no profile exists, get answers profile: null.
The point values, the 14-day half-life and the tier floors are code defaults, readable at trust/policy.
Scores stay between 0 and 100, and two reads less than a second apart decay by nothing.
Reading a profile is not metered.
Access
API & MCP
REST and MCP
Authenticate with a workspace API key as a Bearer token. The base URL is https://api.intramedial.com.
REST endpoints
GET/api/v1/acp/trust/getRead one agent's trust profile.
GET/api/v1/acp/trust/tierRead one agent's profile and its autonomy tier.
GET/api/v1/acp/trust/policyRead the point values, decay and tier floors.
MCP actions
MCPcoordination.trust.getRead a trust profile as an MCP action.
MCPcoordination.trust.observeRecord a manual trust observation as an MCP action.