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…
outcomes.summaryModule 55
Plane module
Impact HQ outcomes
Connect governed agent activity to outcomes you can measure, with every modeled figure shown next to the assumption that produced it.
outcomes.summary reports metrics across nine outcome kinds, graded direct, modeled, partial or unconfigured by whether value came from a measured duration or an assumption. builds the full value ledger, with every figure's provenance traced to the event or assumption behind it.
Intralock · Leases · Parley · Fleet Map
A Trustvice Product
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.
direct, modeled, partial or unconfigured, naming how a metric's value was produced.
provenance
Concrete references behind a figure: specific event ids, the assumption version, the window, or what field was missing.
comparison
The same metrics for the immediately preceding window of equal length, when requested.
Mechanism
Step by step
How it works
An outcome is recorded
record logs one of nine kinds – agent task completed, conflict prevented, settlement closed and others – with an optional directDurationMinutes when the time was actually measured.
Minutes are counted two ways
Measured minutes sum only events that supplied a real duration; minutes without one are modeled by multiplying the event count by that kind's assumption, never defaulted to zero.
Value follows minutes and assumptions
Labor value comes from measured plus modeled minutes at the configured hourly cost; avoided-incident value comes from a separate per-incident assumption. Either stays unconfigured rather than silently reading as zero if its assumption is missing.
Assumptions version, never overwrite
assumptions.set appends a new version rather than replacing the last one, Merkle-receipted over every version so far, and assumptions.history reads the full chain.
Try it
Live demo
Run it from this page
GET/api/v1/acp/outcomes/summary
// No body: this is a GET. Press Run.
Runs in a shared demo workspace with a demo key: anyone can see what it holds, so send nothing private. outcomes.summary docs
Responses
Press Run to send the request on the left to the shared demo workspace.
Runs in a shared demo workspace with a demo key: anyone can see what it holds, so send nothing private.
Code
Live example
A real request
A request in the shape the API accepts, and an example response in the shape the module returns.
GET/api/v1/acp/outcomes/summaryAuthorization: Bearer av_workspace_••••→ 200 { window, assumptionVersion, metrics, comparison? } (no top-level outcomes or assumptions; the full assumptions object comes from assumptions.get, assumptions.history or export)
A finance reviewer reads confidence on each metric and knows immediately which figures came from recorded durations and which from an assumption the organization set itself.
Versioning an assumption honestly
An organization lowers its assumed minutes saved per automated task; the change is a new version, Merkle-receipted, and every past summary still points at the version that was actually in force then.
Exporting a defensible value ledger
export builds a snapshot with every event, every assumption version, the formulas used and a Merkle root over the whole thing, ready to hand to someone outside the team.
Spotting an unconfigured figure early
A monetary value stays unconfigured rather than reading as zero when its assumption is missing, so nobody mistakes an unset number for an actual finding of no value.
When to use something else
Treating a missing assumption as zero savings. An unconfigured metric reports as unconfigured, never a false zero.
Crediting an outcome with no recorded event behind it. Every metric's provenance names the specific events or assumptions it came from.
Calling this module as an MCP or agent action. It has no contract action id; it is reachable only over REST.
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
A measured minutes figure sums only events that actually supplied a real duration, never an estimate presented as a measurement.
Every assumption change is a new version, Merkle-receipted over the full chain so far, never an overwrite of the one before it.
A metric whose required assumption is missing reports unconfigured, never a default of zero that could be mistaken for a real finding.
It does not
That a modeled figure reflects what actually happened. It reflects the organization's own stated assumption applied to a real event count.
That outcomes are complete. Only the nine recorded kinds are tracked; activity outside them produces no metric at all.
That this module is reachable by an agent. It has no MCP or contract action id, unlike several of the modules whose events it records.
Outcomes has no README; the formulas and field names described here come directly from its service code and its own in-code FORMULAS documentation object.
Idempotent assumption writes
assumptions.set is idempotent per key; replaying the same key with a different input is refused as a conflict rather than silently applied twice.
Limits and metering
No MCP or contract action id exists for any route here; it is REST-only.
Only the nine named outcome kinds are tracked; nothing outside them produces a metric.
A metric's modeled value needs its assumption on file; without it, the figure is unconfigured, not estimated some other way.
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/outcomes/summaryRead this window's metrics by confidence.
POST/api/v1/acp/outcomes/recordLog one outcome event.
POST/api/v1/acp/outcomes/exportBuild the full Merkle-receipted value ledger.
MCP actions
This module has no MCP action. Call it over REST from any agent or program.