Home / Standards / AIGS 100
Exposure Draft

AIGS 100 Accountable Ownership

Every AI system and agent has a named, current, human owner and a stated purpose, and ownership survives people changing roles.

Document
AIGS 100, Exposure Draft ED-2026-100
Status
Founding draft, open for member comment
Comment period
60 days from publication
Working Group
TWG-100 Ownership
Effective date
To be set on issuance

1. Objective

To ensure that for every AI system an organization operates, a specific person is accountable for what it is for, what it can reach, what it costs and whether it should keep running.

2. Scope

Applies to AI systems used by or on behalf of the organization, including: AI agents and copilots built on low-code or pro-code platforms; automated flows that invoke AI models; direct model and API connections; AI tool and integration servers (for example Model Context Protocol servers); and non-human identities (service principals, API keys, tokens) used by AI systems.

3. Key terms

Owner of record. The single human, resolvable to an active identity in the organization's directory, accountable for an AI system.

Creator. The identity that built or published the system. A creator is not presumed to be the owner of record.

Ownership roles. Business, technical, security, data and executive owners recorded for higher-risk systems.

Owner unknown. The state of a system for which neither the platform nor the organization can identify an accountable person.

Creator buildsAI system Owner of recordassigned + attests Leaver ormover event Reassignedwithin period Flagged ownerlessescalated Platform reports no owner:recorded as "owner unknown", never assumed
Ownership continuity under AIGS 100.

4. Requirements

100.1The organization shall maintain a current inventory of in-scope AI systems, refreshed automatically where the platform allows and at least monthly otherwise.
100.2Each AI system shall have one owner of record who is a human resolvable to an active directory identity. A creator shall not be recorded as owner of record without that person's acceptance.
100.3For AI systems that act autonomously, reach confidential or personal data, or send data outside the organization, the organization shall also record business, technical, security, data and executive owners.
100.4The owner of record shall attest to the system's purpose, the data it uses and the actions it may take. Attestations shall be versioned and renewed on material change and at least annually.
100.5When an owner of record leaves or changes role, ownership shall be reassigned within a defined period (proposed: 30 days). Systems not reassigned within the period shall be flagged as ownerless and escalated.
100.6Where the platform does not report a creator or owner, the system shall be recorded as "owner unknown". The organization shall not infer or default an owner, and shall report the count of such systems.
100.7Manual changes to ownership shall be limited to authorized administrators, shall replace rather than silently supplement the platform record, and shall be logged with who changed what and when.
100.8Owners shall be able to see the systems assigned to them, and shall not by default see systems owned by others.

5. Evidence

  • Inventory export showing owner of record, ownership roles and last attestation per system.
  • Leaver and mover reassignment log with dates.
  • List of "owner unknown" and ownerless systems with escalation records.
  • Audit log of manual ownership changes.

6. Metrics

MetricDefinition
Ownership coverageSystems with a current owner of record, divided by all in-scope systems.
Owner-unknown shareSystems for which no owner can be identified, divided by all in-scope systems.
Reassignment timeMedian days from leaver event to reassignment.
Attestation currencySystems with an attestation less than 12 months old, divided by owned systems.

7. Basis for conclusions

Field experience shows that a large share of low-code agents in some estates have no owner reported by the platform, and that the people who created agents frequently change roles. Defaulting such agents to an assumed owner creates false accountability. The draft therefore requires an explicit "owner unknown" state and a reassignment clock rather than inference.

This founding draft was prepared by the Secretariat from practical control experience, including the founding sponsor's, and is published for open comment. It names no product and requires none.

8. Questions for respondents

  1. Is 30 days an appropriate reassignment period? Should it vary by risk?
  2. Should every system require the five ownership roles, or only higher-risk systems as proposed?
  3. Is annual re-attestation sufficient for autonomous agents?
Comment on AIGS 100All standards