ISO 23081-1:2017 — Managing Metadata for Records (records metadata)

ISO 23081-1:2017 — Managing Metadata for Records (records metadata) — 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 23081-1:2017: 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.

  1. classification-driven-authority · enforced

    Classification-driven authority: a record's metadata classification sets the authority bar for a…

    Audit events: kye.purpose.request.v1, kye.purpose.admissibility.v1, kye.evidence.decision_map.v1 · Rule packs: kye:rule-pack:chain-of-authority-insight · Constitution: 12 purpose permission

  2. event-history-evidence · enforced

    Event-history evidence: the record's custody/event metadata is bound into the KYE™ evidence pin for the…

    Audit events: kye.evidence.pack.v1, kye.evidence.tool_call.v1 · Rule packs: kye:rule-pack:chain-of-authority-insight · Constitution: 13 resilience loop

  3. agent-metadata-principal-binding · enforced

    Agent-metadata binding: the record's agent metadata resolves to exactly one KYE-resolved principal in one…

    Audit events: kye.purpose.request.v1, kye.evidence.decision_map.v1 · Rule packs: kye:rule-pack:chain-of-authority-insight · Constitution: 52 delegated agent binding

  4. metadata-creation-capture · out-of-scope

    Metadata creation & capture (records-management — owned by Iron Mountain InSight DXP, not KYE™)

    Constitution: 15 mcp and sdk

  5. metadata-management-maintenance · out-of-scope

    Metadata management & maintenance over the lifecycle (records-management — owned by Iron Mountain, not KYE™)

    Constitution: 30 audit worm retention

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 23081-1:2017 specifies the framework for creating, managing and using records-management metadata — describing the record, the agents, the business activity, and the relationships and events over the record's lifecycle. KYE Protocol™ does NOT generate or manage records metadata — Iron Mountain InSight DXP does. KYE Protocol™ CONSUMES records metadata (agent, classification, business activity) as the input signal at the action boundary: the §15 connector maps InSight DXP records-metadata fields → the KYE Protocol™ entity/evidence model. The metadata-creation and metadata-management requirements map out-of-scope; the metadata-driven action-decision (a classification/agent metadata field raising the authority bar before a consequential action) maps enforced. · License: ISO copyright — citation only; KYE™ registry cites clause structure for mapping purposes (no normative text reproduced).

By category

CategoryReqsEnforcedDesignedAdvisoryDeferredCoverage
Metadata-driven authority decision (authority overlay)22000100%
Agent-metadata binding to a KYE-resolved principal (authority overlay)11000100%
Metadata creation & capture (records-management)100000%
Metadata management & maintenance (records-management)100000%

Every requirement → the KYE™ artefact that enforces it

IDTitleStatusKYE™ enforcement
iso-23081.classification-driven-authorityClassification-driven authority: a record's metadata classification sets the authority bar for a consequential AI actionenforcedaudit_events: kye.purpose.request.v1, kye.purpose.admissibility.v1, kye.evidence.decision_map.v1
engines: internal, internal
rule_packs: kye:rule-pack:chain-of-authority-insight
constitution_refs: constitution/12-PURPOSE-PERMISSION.md
iso-23081.event-history-evidenceEvent-history evidence: the record's custody/event metadata is bound into the KYE™ evidence pin for the action decisionenforcedaudit_events: kye.evidence.pack.v1, kye.evidence.tool_call.v1
engines: internal, internal
rule_packs: kye:rule-pack:chain-of-authority-insight
constitution_refs: constitution/13-RESILIENCE-LOOP.md
iso-23081.agent-metadata-principal-bindingAgent-metadata binding: the record's agent metadata resolves to exactly one KYE-resolved principal in one tenantenforcedaudit_events: kye.purpose.request.v1, kye.evidence.decision_map.v1
engines: internal, internal
rule_packs: kye:rule-pack:chain-of-authority-insight
constitution_refs: constitution/52-DELEGATED-AGENT-BINDING.md
iso-23081.metadata-creation-captureMetadata creation & capture (records-management — owned by Iron Mountain InSight DXP, not KYE™)out-of-scopeconstitution_refs: constitution/15-MCP-AND-SDK.md
iso-23081.metadata-management-maintenanceMetadata management & maintenance over the lifecycle (records-management — 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™.