Skip to content
Promenaut

Promenaut joins forces with HSBC as strategic investor and design partner.Read More

For model risk and second line

Can we govern it, and show that we did?

Govern it, and show that you did.

Each completed agent run records which model answered, each decision is kept, and each run ends with a verdict written to a hash-chained ledger. Below, the questions a review asks of Promenaut, with what answers each on the platform.

The governance pack: Governing the Promenaut Workforce and Model Risk Evidence on Promenaut, sent on request.

  1. Model and providerrecorded for each completed agent run
  2. Approvalwho decided, item by item
  3. Roster verdictthe agents that ran, against the roster
  4. Ledgerhash-chained, so a later edit shows
01Your review

The questions, in the order they come.

  • An agent's declared boundary, drawnEach agent's declared boundary is shown as one card with the agent at its centre: the workflows and platform teams that admit it, the agents declared to call on it, the service teams it may call, its declared effects and invocation surfaces, the knowledge it reads, and its preferred model and clearance, with anything the agent does not declare shown as not declared.
  • Declared I/O contractsAn agent declares what it consumes and produces.
  • Versioned, diffable agent configurationAn agent configuration is a versioned object with its own lifecycle: versions can be listed, compared against each other, and published deliberately rather than taking effect on save.
We take you through the answer: see the model risk evidence on a live run →

  • Approval gate on agent workWork can be held for a human decision, approved or rejected individually or in bulk, with the decision history kept and retrievable per workflow.
  • Run quality never suppresses governanceWhether a piece of work needs human review is decided by declared configuration alone.
  • A trust gate between an agent and its changesAn agent can pass a change it has found through a trust gate instead of making it.
We take you through the answer: see the model risk evidence on a live run →

02Everything built for it

What the platform does for you, layer by layer.

Identity and access

  • Service identities are reviewed on a cadence
  • Administrators act only within their enterprise and authority

Approvals, decisions and containment

  • Approval gate on agent work
  • Proposed change inbox
  • Dialled autonomy
  • Run quality never suppresses governance
  • Decision explorer
  • Agent handbrake
  • Suspend an agent everywhere
  • One protocol for decisions a person must make
  • No outside MCP server reaches an agent until it is approved by a second person, or by a super admin who registered it
  • Platform staff can block an outside MCP server for every organisation at once
  • An agent runs an approved public skill in a sandbox with no outside network, and its uses are recorded
  • A trust gate between an agent and its changes
  • Containment rules drain, quarantine, pause or block matching work
  • One governed door for stopping and containing work
  • A held run waits for the decision that holds it
  • A second person approves a proposed directive
  • Brakes on automatic control
  • Containing work by what it touches
  • Runaway agents are suspended automatically
  • An agent that keeps failing on its own configuration is contained automatically
  • One place to govern MCP, in both directions
  • One checked, recorded door for the tools an agent offers a model
  • A control directive can slow matching work down without stopping it
  • A control directive can pause, drain or kill one agent or one team inside a running workflow
  • One Approvals screen for what the control engine is waiting on
  • An approval gate holds matching runs or calls until a person decides
  • Automatic step-up of containment for a runaway agent

Model risk

  • Contract truthfulness monitoring
  • Model risk oversight console
  • Agent call monitoring
  • Run-end roster verdict
  • Declared versus actual conformance
  • User reliance tracking
  • Workflow-run ratings
  • Tamper-evident risk ledger
  • Model inventory
  • Model provenance and self-drift
  • Agent run health and trends
  • Model risk access audit
  • Reliance evidence export
  • Run evidence export
  • An agent's declared boundary, drawn
  • A diagram of one run for auditors
  • Conversation oversight: replay a person's chat
  • Whether each agent, team and run passed its model risk checks
  • Pausing and stopping work is requested through control directives, not through model risk
  • Policy rules that record, propose or apply a control directive
  • A record of when each model was reviewed, by whom, and the outcome
  • One cost figure for each run and agent, with its parts by kind
  • One finding for failures that share a cause across the fleet
  • Judging whether a run stayed within the intent it was launched with

Performance and review

  • Per-agent and per-version performance
  • Agents are reviewed on a cycle
  • Reviewed by a manager, a peer, a person, or the platform
  • Promote, maintain, or put on a plan
  • An improvement plan with a target and a deadline
  • The cycle starts itself
  • Agent grading
  • Agents evaluate other agents' work as it runs

Audit trails

  • Administrative audit trail
  • Agent lifecycle audit log
  • Seam calls leave an activity record
  • Old capability audit records are archived before they leave the database
  • Audit ledger anchored outside the database

Credits and budgets

  • What a run has spent, while it runs
More on Control →

Weighing us against the tools you already know? See how we compare, with sources →

How the second line’s questions are answered for agents, run by run. Model risk for AI agents →

03The pack

The full answers, written for you.

Governing the Promenaut WorkforceAbout 20 minutes

Model Risk Evidence on PromenautAbout 30 minutes

Get the governance pack

Bring your model risk team.

Walk a live run from launch to verdict: what ran, what was approved, and the evidence the platform records.

See the model risk evidence on a live run