01
Which release did this evidence support?
Show the exact model, data, eval run, approval, and monitoring plan behind a customer-facing claim.
Ship AI systems you can defend.
Ormedian turns high-stakes AI releases into living evidence trails: release contracts, evaluation gates, monitoring signals, provenance, and Assurance Packs.
View the open-source scaffold on GitHub →A model release moves through evidence gates and monitoring into a living Assurance Pack.
Release evidence trail
Release contract
Evaluation gate
Risk control
Monitoring
claims-routing-v4.1
Intended use Complete
Evaluation Passed
Risk register Controlled
Monitoring Live
Defensibility fails when evidence loses its release context.
Metrics, risk notes, logs, approvals, and incident context usually exist. They just do not travel together as one release record. Ormedian makes the release itself the organizing unit.
02
What changed, and who accepted the risk?
Trace the release diff, risk owner, and control that was in force when live behavior shifted.
03
Can you reproduce the decision trail?
Turn scattered notebooks, dashboards, documents, and chat threads into one defensible artifact.
Assurance Packs
One living dossier per AI release.
An Assurance Pack is the destination of the release evidence trail: compact enough to inspect, complete enough to defend.
claims-routing-v4.1
Intended use
Route enterprise support claims to the right specialist queue with human review on uncertain or policy-sensitive cases.
- claims-routing-v4.1
Release gates
Routing accuracy delta
Policy override rate
Open critical risks
Manual review required for claims above the financial-risk threshold.
Intended use, scope, assumptions, exclusions, and policy constraints
Evaluation results with run IDs, baselines, thresholds, and failure notes
Risk register entries with owners, controls, residual risk, and review cadence
Monitoring thresholds, alert rules, incidents, and escalation paths
Provenance linking data, model, policy, reviewer, and release decision
Approval history that stays coupled to the deployed version
Workflow
Governance becomes part of the release path.
Ormedian turns review gates into concrete outputs, so the pack is assembled while work happens instead of after everyone has moved on.
- 01
Define release contract
Capture intended use, exclusions, success metrics, evaluation criteria, and policy constraints before review.
- 02
Evaluate against gates
Attach run IDs, baselines, thresholds, failures, and deltas from the evaluation suite.
- 03
Monitor deployed behavior
Connect production signals, drift thresholds, incident notes, policy violations, and alert ownership.
- 04
Bundle current evidence
Publish the Assurance Pack as the current record for the deployed version and release decision.
claims-routing-v4.1
-
Define intended use
-
Run evaluation suite
-
Review residual risk
-
Attach monitoring plan
-
Bundle release evidence
After deployment
Evidence keeps moving after launch.
Monitoring signals, provenance edges, incidents, and approvals remain coupled to the deployed version instead of drifting into separate operational tools.
Release health cockpit
Signal trail
Evidence updates
Financial advice classifier exceeded review threshold.
New market segment observed in production traffic.
Monitoring evidence linked to the current release record.
Provenance graph connecting Eval Run, Dataset, Model, Policy, Reviewer, and Decision with a fixed release evidence topology.
Release evidence graph
Review moments
Built for the moments where claims need evidence.
Regulated launch
Package intended use, evaluation coverage, residual risks, monitoring plans, and approvals before production.
Customer evidence request
Respond with a release-specific assurance record instead of scattered screenshots and ad hoc documents.
Drift or incident
Trace what changed, which thresholds fired, who reviewed it, and which control applied.
Model release review
Give engineering, product, risk, and compliance the same evidence record before sign-off.
Procurement review
Show how the AI system is evaluated, monitored, governed, and kept under control.
Policy or ownership change
Keep controls, owners, assumptions, exclusions, and review cadence explicit.
Evidence tied to deployed versions
Reproducible evaluation references
Risk controls with named owners
Monitoring plans that stay current
Early access
Start with one release you need to defend.
Join the waitlist for a sample Assurance Pack, beta access, and practical templates for evaluation, monitoring, provenance, and release governance.