OIS · Domains

Domains — how an organisation becomes visible.

A Domain is an area of responsibility inside an organisation. It is not just a department: it is where OIS connects mandate, evidence, rules, boundaries, recommendations and human decisions.

What a Domain is

A Domain is an area of responsibility — Editorial, Legal Matters, Trust, Operations, Commercial, Compliance. It is more than a department: it is where OIS brings together what the area is responsible for, the evidence behind it, the rules it follows, the boundaries it respects, the recommendations it produces and the decisions that need a person.

The formula

A mandate (what it is responsible for), the intelligences bound to it, its own rules, the shared Constitutional Contract, and explicit boundaries on what it may see and touch.

Domain = Mandate × OIS Engines × Rules × Constitutional Contract × Boundaries

Why Domains matter

Most organisations are a tangle of tools, folders and inboxes. Domains give that tangle a shape an owner recognises: areas of responsibility, each with its own health, priorities and risks. You stop managing software and start seeing your organisation.

How Domains make an organisation visible

Each Domain reports the same way, so the whole organisation is legible side by side. One glance shows which areas are healthy, which need attention, where the risks are, what evidence supports each signal, and which decisions are waiting for a person.

What each Domain has

  • A mandate — what it is responsible for
  • Bound intelligence layers — the OIS engines wired to it
  • Rules — the domain-specific policies it follows
  • Boundaries — what it may see and touch, and what it may not
  • Evidence — the source behind every signal
  • Recommendations — advisory next steps
  • Human decisions — the choices that only a person may make

The Constitutional Contract

  • Health
  • KPIs
  • Confidence
  • Objectives
  • Current priorities
  • Risks
  • Decisions required
  • Human tasks
  • Intelligence signals
  • History

Honest-State in a Domain

A Domain must show what it can measure — and what it cannot. There is no fake green status and no decorative confidence: if a Domain has no data for something, it is shown as not measured, never disguised as healthy.

Different Domains, different emphasis

DomainEmphasis
EditorialObserve → Understand → Recommend
Legal MattersObligation → Decision → Outcome
OperationsSignal → Risk → Action
CommercialOpportunity → Follow-up → Revenue outcome
TrustEvidence → Confidence → Provenance
ConnectorScope → Inventory → Evidence → Not measured

Example Domains

Editorial Domain

For media, communications or publishing. Tracks coverage, freshness, sources, story gaps, review queues and editorial recommendations.

Legal Matters Domain

For law firms or legal departments. Tracks cases, deadlines, hearings, obligations, next actions, compliance gates and outcomes.

Trust Domain

Tracks sources, provenance, evidence, uncertainty, confidence and review status.

Operations Domain

Tracks processes, incidents, bottlenecks, obligations, system state and operational risks.

Commercial Domain

Tracks leads, pipeline, follow-ups, invoices, renewals, revenue risks and opportunities.

Compliance Domain

Tracks rules, approvals, obligations, exceptions, audit trails and required decisions.

Connector Domain

Tracks connected systems, scope, inventory, permissions, what was analysed and what remains not measured.

From organisation to decision

The same path in every Domain — and a person decides at the end.

OrganisationDomainsConstitutional ContractEvidence-backed signalsRecommendationsHuman decisions

See your organisation clearly.

Start with a read-only OISA audit — what is known, what is missing and what to decide.

Contact us