# ISO/IEC 42001:2023 Clause 8 artifact mapping

ISO/IEC 42001:2023 - Information technology - Artificial intelligence - Management system.

This document lists PEAC surfaces that can be used as supporting evidence toward ISO/IEC 42001:2023 Clause 8 (Operational planning and control) objectives. The scope is narrow: every row points at a concrete PEAC artifact (spec, fixture, test, package, or generated artifact) that an operator of an AI management system may reference when building their Clause 8 operational controls. Every row also states explicitly what PEAC does not do for that row; the operator is responsible for the operational decisions, risk treatments, and management-system activities themselves.

This document is not a certification. It is not a substitute for an AIMS implementation. It is not a claim that PEAC satisfies Clause 8 end-to-end. It is a mapping that helps an operator route a Clause 8 checklist to the underlying PEAC artifacts where supporting evidence exists.

## Scope and framing

- **Standard:** ISO/IEC 42001:2023.
- **Clause scope:** Clause 8 (Operational planning and control). Cross-references to Clauses 6.1 (Actions to address risks and opportunities), 7.5 (Documented information), 9 (Performance evaluation), and 10 (Improvement) are listed per row where relevant.
- **Artifact scope:** PEAC surfaces that an operator can reference as supporting artifacts. The operator owns the management-system activities.
- **Non-claim:** PEAC does not implement an AIMS. PEAC provides portable signed interaction records and verification surfaces that an AIMS can consume as evidence inputs. Risk assessment, risk treatment, impact assessment, decision-making, and management review are operator-owned.

## Column legend

- **Clause:** ISO/IEC 42001:2023 clause number and short objective phrase.
- **PEAC primitive:** the PEAC concept that produces the supporting evidence.
- **Artifact surface:** concrete file, package, spec, fixture, or API endpoint under this repository. Every non-out-of-scope row MUST include at least one outward-facing stable artifact surface (one of `docs/`, `specs/`, `contracts/`, `surfaces/`, `packages/schema/openapi/`, or `REPO_SURFACE_STATUS.json`); internal `src/` paths may appear only as secondary links.
- **Verification hint:** concrete path, endpoint, fixture, or CI command an evaluator runs to verify the row.
- **Coverage qualifier:** one of `supports`, `can be used as evidence toward`, `provides primary artifact for`, `provides supporting artifact for`, `helps evidence`, `out-of-scope for PEAC`.
- **Non-claim:** explicit statement of what PEAC does not do for this row; one of `PEAC does not do X`, `operator-owned`, `requires upstream attestation`, `evidence only; not a conformance claim`.
- **Cross-reference:** related ISO 42001 clauses and PEAC trust artifacts; markdown links in this column must resolve.

## Mapping

| Clause                                                                  | PEAC primitive                                                                                                                                     | Artifact surface                                                                                                                                                                                                               | Verification hint                                                                                                                                                                                                                                      | Coverage qualifier               | Non-claim                                                                                                                                                                                              | Cross-reference                                                                                            |
| ----------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------- |
| 8.1 Operational planning and control                                    | Portable signed interaction record (Wire 0.2 `interaction-record+jwt`)                                                                             | [`docs/specs/WIRE-0.2.md`](../specs/WIRE-0.2.md), [`packages/schema/openapi/verify.yaml`](../../packages/schema/openapi/verify.yaml), [`docs/specs/PROTOCOL-BEHAVIOR.md`](../specs/PROTOCOL-BEHAVIOR.md)                       | Issue a record and `POST /v1/verify` against the OpenAPI in [`packages/schema/openapi/verify.yaml`](../../packages/schema/openapi/verify.yaml); inspect the round-trip claims.                                                                         | provides supporting artifact for | evidence only; not a conformance claim. The operator owns the operational plan and the control decisions; PEAC provides the record that evidences what the operational path observed.                  | ISO 42001 Clause 6.1; [`docs/SLO.md`](../SLO.md), [`docs/STABILITY-CONTRACT.md`](../STABILITY-CONTRACT.md) |
| 8.1 Operational planning and control (change control)                   | Stability contract classifying every public surface `stable` / `experimental` / `deprecated` / `internal-only`                                     | [`docs/STABILITY-CONTRACT.md`](../STABILITY-CONTRACT.md), [`docs/DEPRECATION_POLICY.md`](../DEPRECATION_POLICY.md)                                                                                                             | Regenerate status via `pnpm verify:surface-status`; inspect [`docs/STABILITY-CONTRACT.md`](../STABILITY-CONTRACT.md) classification rows.                                                                                                              | supports                         | operator-owned. PEAC publishes its own stability contract for its own surfaces; the operator owns the AIMS change-control process.                                                                     | ISO 42001 Clause 7.5; [`docs/SURFACE_STATUS.md`](../SURFACE_STATUS.md)                                     |
| 8.1 Operational planning and control (external service management)      | Reference verifier (self-hostable, tenantless) and Hosted Verify contract normalization                                                            | [`surfaces/reference-verifier/`](../../surfaces/reference-verifier/), [`docs/HOSTED_VERIFY_CONTRACT.md`](../HOSTED_VERIFY_CONTRACT.md), [`docs/TRUST-ARTIFACTS.md`](../TRUST-ARTIFACTS.md)                                     | Run [`surfaces/reference-verifier/smoke.sh`](../../surfaces/reference-verifier/smoke.sh) against the reference deployment.                                                                                                                             | supports                         | operator-owned. PEAC publishes verification-surface choices; the operator selects and governs the verification topology used in their AIMS.                                                            | ISO 42001 Annex A A.10; [`docs/TRUST-ARTIFACTS.md`](../TRUST-ARTIFACTS.md)                                 |
| 8.2 AI risk assessment (input evidence)                                 | Signed interaction record with issuer identity, subject, purpose, and timestamp binding                                                            | [`docs/specs/WIRE-0.2.md`](../specs/WIRE-0.2.md), [`packages/schema/openapi/verify.yaml`](../../packages/schema/openapi/verify.yaml), [`specs/conformance/requirement-ids.json`](../../specs/conformance/requirement-ids.json) | Sample `specs/conformance/` fixtures; verify each record's issuer, subject, purpose, and `iat` claims against the schema declared in [`docs/specs/WIRE-0.2.md`](../specs/WIRE-0.2.md).                                                                 | can be used as evidence toward   | requires upstream attestation. The record attests what the issuing party observed; PEAC does not perform the risk assessment.                                                                          | ISO 42001 Clause 6.1.2; [`docs/THREAT_MODEL.md`](../THREAT_MODEL.md)                                       |
| 8.2 AI risk assessment (AI-specific characteristics)                    | Structured 10-pillar taxonomy on every record (Access, Attribution, Commerce, Consent, Compliance, Privacy, Provenance, Safety, Identity, Purpose) | [`specs/kernel/registries.json`](../../specs/kernel/registries.json), [`docs/specs/REGISTRIES.md`](../specs/REGISTRIES.md)                                                                                                     | Enumerate pillar keys in [`specs/kernel/registries.json`](../../specs/kernel/registries.json); cross-check against record `pillars` field documented in [`docs/specs/WIRE-0.2.md`](../specs/WIRE-0.2.md).                                              | helps evidence                   | PEAC does not assess risk. The pillar taxonomy classifies the observed interaction; the operator applies their risk assessment methodology to the classified records.                                  | ISO 42001 Clause 6.1.2                                                                                     |
| 8.3 AI risk treatment (evidence of treatment decisions)                 | Policy-binding block with JCS-hashed policy digest (three-state result: `verified` / `failed` / `unavailable`)                                     | [`docs/specs/WIRE-0.2.md`](../specs/WIRE-0.2.md), [`specs/conformance/fixtures/wire-02/policy-binding/`](../../specs/conformance/fixtures/wire-02/policy-binding/)                                                             | Run fixtures under [`specs/conformance/fixtures/wire-02/policy-binding/`](../../specs/conformance/fixtures/wire-02/policy-binding/); verify the three-state result per the policy-binding section of [`docs/specs/WIRE-0.2.md`](../specs/WIRE-0.2.md). | provides supporting artifact for | evidence only; not a conformance claim. PEAC records the policy that was in force at interaction time; the operator owns the policy content, the treatment decision, and the residual-risk acceptance. | ISO 42001 Clause 6.1.3                                                                                     |
| 8.3 AI risk treatment (enforcement vs observation boundary)             | Mapper boundary guard (`assertExplicitFinality`) rejecting finality synthesis across commerce observations                                         | [`docs/compatibility/commerce-protocol-coverage.md`](../compatibility/commerce-protocol-coverage.md), [`docs/specs/COMMERCE-EVIDENCE.md`](../specs/COMMERCE-EVIDENCE.md)                                                       | Run `pnpm --filter @peac/adapter-core test` against the finality test suite; review the boundary rules in [`docs/compatibility/commerce-protocol-coverage.md`](../compatibility/commerce-protocol-coverage.md).                                        | supports                         | PEAC does not enforce. PEAC preserves what the upstream attested and refuses to synthesize finality where none was declared; the operator owns treatment enforcement elsewhere.                        | ISO 42001 Clause 8.3                                                                                       |
| 8.4 AI system impact assessment (observational input)                   | Verification record set carrying observed interactions across runtime, tool, API, commerce, and cross-runtime surfaces                             | [`docs/compatibility/core-use-case-coverage.md`](../compatibility/core-use-case-coverage.md), [`specs/conformance/`](../../specs/conformance/)                                                                                 | Sample records from each covered surface in [`docs/compatibility/core-use-case-coverage.md`](../compatibility/core-use-case-coverage.md); verify each against [`specs/conformance/`](../../specs/conformance/) fixtures.                               | provides supporting artifact for | operator-owned. PEAC records the interactions that an impact assessment may use as evidence; PEAC does not perform the impact assessment or determine affected rights-holders.                         | ISO 42001 Clause 8.4                                                                                       |
| Clause 7.5 Documented information (retention)                           | Portable signed record format independent of vendor storage; offline verifiable                                                                    | [`docs/specs/WIRE-0.2.md`](../specs/WIRE-0.2.md), [`docs/HOW-IT-WORKS.md`](../HOW-IT-WORKS.md)                                                                                                                                 | Verify an archived record offline via the verification path in [`docs/specs/WIRE-0.2.md`](../specs/WIRE-0.2.md); confirm no network I/O is required.                                                                                                   | supports                         | operator-owned. PEAC records are offline-verifiable artifacts; the operator owns retention windows, storage, and access control for their documented information system.                               | ISO 42001 Clause 7.5; [`docs/KEY-CUSTODY-AND-TENANCY.md`](../KEY-CUSTODY-AND-TENANCY.md)                   |
| Clause 9.1 Monitoring, measurement, analysis and evaluation             | Benchmark methodology, published SLO baseline stamps, regression-aware verification path                                                           | [`docs/BENCHMARK-METHODOLOGY.md`](../BENCHMARK-METHODOLOGY.md), [`docs/SLO.md`](../SLO.md), [`specs/benchmarks/`](../../specs/benchmarks/)                                                                                     | Reproduce benchmarks per [`docs/BENCHMARK-METHODOLOGY.md`](../BENCHMARK-METHODOLOGY.md); compare results to baseline in [`specs/benchmarks/`](../../specs/benchmarks/).                                                                                | helps evidence                   | operator-owned. PEAC publishes its own engineering SLOs and benchmark discipline; the operator owns AIMS performance evaluation.                                                                       | ISO 42001 Clause 9.1                                                                                       |
| Clause 9.2 Internal audit (evidence inputs)                             | Machine-readable contracts + regenerated status artifacts + conformance IDs                                                                        | [`contracts/api/`](../../contracts/api/), [`REPO_SURFACE_STATUS.json`](../../REPO_SURFACE_STATUS.json), [`specs/conformance/requirement-ids.json`](../../specs/conformance/requirement-ids.json)                               | Sample rows from [`contracts/api/`](../../contracts/api/) and [`REPO_SURFACE_STATUS.json`](../../REPO_SURFACE_STATUS.json); cross-check against [`specs/conformance/requirement-ids.json`](../../specs/conformance/requirement-ids.json).              | provides supporting artifact for | evidence only; not a conformance claim. PEAC provides machine-readable surfaces the auditor can sample; the operator schedules and conducts the audit.                                                 | ISO 42001 Clause 9.2                                                                                       |
| Clause 10.2 Nonconformity and corrective action (traceability)          | Receipt reference (`receipt_ref` = SHA-256 of the JWS) enabling back-reference to the exact record that surfaced the nonconformity                 | [`docs/specs/EVIDENCE-CARRIER-CONTRACT.md`](../specs/EVIDENCE-CARRIER-CONTRACT.md), [`docs/specs/WIRE-0.2.md`](../specs/WIRE-0.2.md)                                                                                           | Extract `receipt_ref` per [`docs/specs/EVIDENCE-CARRIER-CONTRACT.md`](../specs/EVIDENCE-CARRIER-CONTRACT.md); confirm the hash matches the JWS it references.                                                                                          | can be used as evidence toward   | operator-owned. PEAC enables pinning a corrective action to the exact observed record; the operator owns the corrective-action process.                                                                | ISO 42001 Clause 10.2                                                                                      |
| Annex A A.2 Policies for AI (evidence of enforcement)                   | Policy digest in record + three-state policy-binding result                                                                                        | [`docs/specs/WIRE-0.2.md`](../specs/WIRE-0.2.md), [`specs/conformance/fixtures/wire-02/policy-binding/`](../../specs/conformance/fixtures/wire-02/policy-binding/)                                                             | Inspect the `policy.binding` section of [`docs/specs/WIRE-0.2.md`](../specs/WIRE-0.2.md); run policy-binding fixtures.                                                                                                                                 | provides supporting artifact for | PEAC does not write policy. The operator owns the policy content and the determination that the observed digest matches the intended policy.                                                           | ISO 42001 Annex A A.2                                                                                      |
| Annex A A.6 AI system lifecycle (stage evidence)                        | Wire 0.2 record `type` (reverse-DNS / URI) plus 12 typed extension groups                                                                          | [`docs/specs/WIRE-0.2.md`](../specs/WIRE-0.2.md), [`specs/kernel/registries.json`](../../specs/kernel/registries.json)                                                                                                         | Enumerate registered type URIs in [`specs/kernel/registries.json`](../../specs/kernel/registries.json); inspect type-to-extension enforcement in [`docs/specs/WIRE-0.2.md`](../specs/WIRE-0.2.md).                                                     | helps evidence                   | operator-owned. PEAC records interaction type; the operator owns lifecycle-stage classification and stage-transition control.                                                                          | ISO 42001 Annex A A.6                                                                                      |
| Annex A A.7 Data for AI systems (provenance linkage)                    | Attribution extension group, content-signal extension, SLSA/in-toto supply-chain provenance artifacts                                              | [`docs/profiles/attribution.md`](../profiles/attribution.md), [`packages/mappings/intoto/`](../../packages/mappings/intoto/), [`packages/mappings/slsa/`](../../packages/mappings/slsa/)                                       | Run `pnpm --filter @peac/mappings-intoto test` and `pnpm --filter @peac/mappings-slsa test`; inspect attribution profile in [`docs/profiles/attribution.md`](../profiles/attribution.md).                                                              | supports                         | requires upstream attestation. PEAC carries attribution links observed on the record; upstream data governance attests provenance.                                                                     | ISO 42001 Annex A A.7                                                                                      |
| Annex A A.9 Use of AI systems (purpose binding)                         | Declared-purpose claim on every record + purpose pillar classification                                                                             | [`docs/profiles/purpose.md`](../profiles/purpose.md), [`docs/specs/WIRE-0.2.md`](../specs/WIRE-0.2.md)                                                                                                                         | Issue a record with a declared purpose; verify the purpose claim round-trips per [`docs/specs/WIRE-0.2.md`](../specs/WIRE-0.2.md) and matches the purpose profile in [`docs/profiles/purpose.md`](../profiles/purpose.md).                             | provides supporting artifact for | operator-owned. PEAC records the declared purpose and the interaction's purpose classification; the operator determines whether the declared purpose matches intended use and authorizes use.          | ISO 42001 Annex A A.9                                                                                      |
| Annex A A.10 Third-party and customer relationships (evidence exchange) | Portable signed records verifiable across organization, vendor, and runtime boundaries                                                             | [`docs/WHERE-IT-FITS.md`](../WHERE-IT-FITS.md), [`docs/specs/VERIFIER-SECURITY-MODEL.md`](../specs/VERIFIER-SECURITY-MODEL.md)                                                                                                 | Verify a record produced by one party against a verifier operated by another party; follow the cross-boundary flow in [`docs/WHERE-IT-FITS.md`](../WHERE-IT-FITS.md).                                                                                  | supports                         | operator-owned. PEAC enables portable evidence exchange; the operator owns the third-party relationship terms and the data-sharing agreements that authorize the exchange.                             | ISO 42001 Annex A A.10                                                                                     |

## What PEAC does not do for Clause 8

- PEAC does not implement an AI management system.
- PEAC does not perform AI risk assessment, risk treatment, or impact assessment.
- PEAC does not write organizational policy, make authorization decisions, or conduct management reviews.
- PEAC does not replace documented-information retention processes.
- PEAC does not schedule, plan, or conduct internal audits.
- PEAC does not determine conformity with any certifiable standard.

## Related documents

- [EU AI Act Annex IV mapping](EU-AI-ACT-ANNEX-IV-MAPPING.md)
- [Trust artifacts](../TRUST-ARTIFACTS.md)
- [SLO](../SLO.md)
- [Stability contract](../STABILITY-CONTRACT.md)
- [Threat model](../THREAT_MODEL.md)
- [Security operations](../SECURITY-OPERATIONS.md)
- [Key custody and tenancy](../KEY-CUSTODY-AND-TENANCY.md)
