Governance & privacy

Inventory, risk tiers, approvals, evidence and data-handling obligations for agentic systems in the enterprise.

In Governance & privacy

39 articles
Evaluation & assurance6 MIN READ

What good client-controlled AI evaluation looks like

Client control means owning the decision standard, representative cases, evidence access and release authority—not forcing every test to be built or run internally.

Governance & privacy6 MIN READ

Authority boundaries for procurement agents

A procurement agent may discover, compare and prepare, but supplier commitments require explicit mandates, separation and evidence.

Architecture & engineering6 MIN READ

The anatomy of a tool-using AI agent

A tool-using agent is a controlled system around a model, not a model with an API key. Map its runtime layers before deciding what to test, trust or release.

Governance & privacy6 MIN READ

The responsibility map every AI partnership needs

A useful responsibility map connects each AI decision and artefact to a named accountable owner, a performing role, required contributors and evidence of completion.

Governance & privacy7 MIN READ

How to build an evidence register for an AI system

An evidence register should connect each claim and requirement to versioned artefacts, review decisions, known gaps and the conditions under which evidence expires.

Governance & privacy6 MIN READ

What changes when an AI agent can modify itself?

Self-modification turns runtime learning into controlled software change. Separate what may adapt, require evidence for promotion and preserve a recoverable baseline.

Strategy & transformation6 MIN READ

Who owns an AI agent after launch?

Live agents cut across product, operations, risk and technology. One accountable service owner needs explicit decision rights supported by named control owners.

A little more clarity

Questions worth asking.

Start with the questions that shape a better decision.

Which enterprise agent questions does the Softlander blog examine?

The blog examines where agents create business value, how teams define release evidence, how authority and tool access should be bounded, and how engineering, security and governance owners can make a shared decision.

Who are the articles written for?

They are written for product, engineering, AI platform, security, governance and transformation leaders responsible for moving an agent workflow from idea or pilot towards accountable operation.

How do the articles relate to Softlander’s services?

Articles explain the problems and decision methods behind the consultancy’s service direction. They are educational material and do not replace a scoped review of an organisation’s actual system.