Skip to main content

Acquisition, Entitlement & Consumption

AIPS separates discovery, acquisition, and consumption.

Discover Product
-> evaluate trust and fitness
-> acquire/request entitlement
-> resolve governed Product port/package
-> consume under contract

The marketplace is therefore not the Product's consumption layer by default.

Access policy​

A listing should declare an access policy such as:

  • Open;
  • Internal;
  • Restricted;
  • Licensed;
  • Contracted.

The access policy describes how a consumer becomes entitled. It does not change Product Family or APT.

Acquisition mechanisms​

Typical mechanisms include:

  • Request Access;
  • Self-Service Provision;
  • Subscribe;
  • License;
  • Purchase;
  • Entitlement Only.

A Product may support more than one mechanism.

Consumption ports​

After entitlement, consumers use governed ports or packages declared by the Product realization. Examples include:

  • synchronous API;
  • event stream;
  • batch interface;
  • interactive interface;
  • agent/tool protocol;
  • embedded runtime interface;
  • downloadable package;
  • physical/control interface.

Each port should reference a machine-readable contract where applicable.

Consumer obligations​

Access to an AI Product may be conditional on:

  • intended-use declaration;
  • consumer risk acceptance;
  • human-oversight requirements;
  • downstream logging/audit obligations;
  • prohibited-use compliance;
  • license or commercial terms;
  • dependency/version compatibility.

Consumption currentness​

An entitlement does not make stale trust evidence current. Continuous Assurance may suspend or constrain consumption when qualification, governance, dependency, or assurance currentness changes materially.

Principle: Acquisition grants a governed right to consume; it does not override Product trust state.

Post-consumption evidence​

After entitlement and consumption, usage and value evidence flows to COVP — Consumption Observation & Value Plane rather than back into marketplace ontology directly.

COVP may capture:

  • usage telemetry;
  • consumer feedback;
  • intended-use-specific fitness assessments;
  • value-realization evidence;
  • adverse outcome / incident signals.

The marketplace may display a governed summary of this evidence, but raw ratings or usage volume must not be treated as intrinsic Product classification or risk evidence by themselves.