ISO 16175-1:2020 — Processes and Functional Requirements for Software for Managing Records (digital records)

ISO 16175-1:2020 — Processes and Functional Requirements for Software for Managing Records (digital records) — 100% of in-scope requirements covered.

5 requirements · 3 in scope (3 enforced) · 2 out-of-scope (outside KYE™’s authority layer). The 100% is weighted over the in-scope base.

ISO 16175-1:2020: requirement → the KYE™ artefact that enforces it

Demo data

You learn: Which requirements KYE™ enforces at runtime and with which artefact. You can: Walk the requirements.

How this widget is built
Demonstrates
KYE™ Compliance Mapping Rail™
Components
  • Framework requirement (clause)
  • Coverage status
  • KYE™ enforcement artefact (event, decision-record field, Evidence Pack™ entry)
Flow
Clause → status → the KYE™ artefact that enforces it, enforced requirements first. Architecture diagram
Used on

Source: ISO 16175-1:2020 specifies the principles and functional requirements for software that creates and manages digital records — capture, identification, classification, access control, retention/disposition, and audit trail. KYE Protocol™ is NOT records-management software — Iron Mountain InSight DXP is. KYE Protocol™ governs ACTION (who was authorised to act on a digital record at the moment it drives a consequential AI action), not the management of the record itself. The capture / classification / retention functional requirements map out-of-scope (records-management software); the audit-trail and access-decision overlay at the action boundary maps enforced (KYE Protocol™'s chain-of-authority). · License: ISO copyright — citation only; KYE™ registry cites clause structure for mapping purposes (no normative text reproduced).

By category

CategoryReqsEnforcedDesignedAdvisoryDeferredCoverage
Action-decision audit trail (authority overlay)22000100%
Access-control decision at the action boundary (authority overlay)11000100%
Capture & classification functional requirements (records-software)100000%
Retention & disposition functional requirements (records-software)100000%

Every requirement → the KYE™ artefact that enforces it

IDTitleStatusKYE™ enforcement
iso-16175.action-audit-trailAction-decision audit trail: every consequential AI action over a digital record emits an immutable, tamper-evident governance audit entryenforcedaudit_events: kye.evidence.pack.v1, kye.replay.proof.v1, kye.compliance.attestation.v1
engines: internal, internal
rule_packs: kye:rule-pack:chain-of-authority-insight
constitution_refs: constitution/30-AUDIT-WORM-RETENTION.md
iso-16175.replayable-decision-recordReplayable decision record: the action decision is reconstructable offline from public keys aloneenforcedaudit_events: kye.replay.context_seal.v1, kye.replay.proof.v1
engines: internal, internal
rule_packs: kye:rule-pack:chain-of-authority-insight
constitution_refs: constitution/13-RESILIENCE-LOOP.md
iso-16175.access-control-decisionAccess-control decision at the action boundary: refuse an unauthorised AI action on a classified digital recordenforcedaudit_events: kye.purpose.request.v1, kye.purpose.admissibility.v1
engines: internal, internal
rule_packs: kye:rule-pack:chain-of-authority-insight
constitution_refs: constitution/12-PURPOSE-PERMISSION.md
iso-16175.capture-classification-functionalCapture & classification functional requirements (records-software — owned by Iron Mountain InSight DXP, not KYE™)out-of-scopeconstitution_refs: constitution/15-MCP-AND-SDK.md
iso-16175.retention-disposition-functionalRetention & disposition functional requirements (records-software — owned by Iron Mountain, not KYE™)out-of-scopeconstitution_refs: constitution/30-AUDIT-WORM-RETENTION.md

Canonical KYE™ surfaces referenced on this page: KYE Protocol™.