---
title: "DoD 5015.02-STD — Electronic Records Management Software Applications Design Criteria — KYE Protocol™ coverage"
description: "DoD 5015.02-STD — Electronic Records Management Software Applications Design Criteria coverage by KYE Protocol™ — every requirement bijection-mapped to the KYE™ artefact that enforces it."
url: https://kyeprotocol.com/compliance/dod-5015-2/
lang: en
source: "KYE Protocol"
---

> DoD 5015.02-STD — Electronic Records Management Software Applications Design Criteria coverage by KYE Protocol™ — every requirement bijection-mapped to the KYE™ artefact that enforces it.

DoD 5015.02-STD — Electronic Records Management Software Applications Design Criteria

# DoD 5015.02-STD — Electronic Records Management Software Applications Design Criteria — 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.

**Source:** DoD 5015.02-STD sets the design criteria for Records Management Application (RMA) software — declaring records, categorisation by record category / file plan, access controls, audit, and disposition/transfer. KYE Protocol™ is NOT an RMA — Iron Mountain InSight DXP plus a records system is. KYE Protocol™ governs ACTION authority at the boundary where a managed record drives a consequential AI action. The RMA design criteria (record declaration, file plan, disposition) map out-of-scope; the access-control decision and audit-of-the-action-decision overlay maps enforced. · **License:** DoD 5015.02-STD is a US Department of Defense standard published in the public domain; KYE™ registry cites its criteria structure for mapping purposes.

## By category

| Category | Reqs | Enforced | Designed | Advisory | Deferred | Coverage |
| --- | --- | --- | --- | --- | --- | --- |
| Access-control decision at the action boundary (authority overlay) | 2 | 2 | 0 | 0 | 0 | **100%** |
| Audit of the action decision (authority overlay) | 1 | 1 | 0 | 0 | 0 | **100%** |
| Record declaration & categorisation / file plan (RMA criteria) | 1 | 0 | 0 | 0 | 0 | **0%** |
| Disposition & transfer (RMA criteria) | 1 | 0 | 0 | 0 | 0 | **0%** |

## Every requirement → the KYE™ artefact that enforces it

| ID | Title | Status | KYE™ enforcement |
| --- | --- | --- | --- |
| `dod-5015-2.access-control-action-decision` | Access-control at the action boundary: refuse a consequential AI action on a managed record without the required authority | enforced | **audit\_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` |
| `dod-5015-2.named-authority-binding` | Named-authority binding: every consequential action on a managed record is attributable to a named principal | enforced | **audit\_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/36-GOVERNEDUI.md` |
| `dod-5015-2.action-decision-audit` | Audit of the action decision: an immutable governance audit entry for every consequential action on a managed record | enforced | **audit\_events**: `kye.evidence.pack.v1`, `kye.replay.proof.v1` **engines**: `internal`, `internal` **rule\_packs**: `kye:rule-pack:chain-of-authority-insight` **constitution\_refs**: `constitution/30-AUDIT-WORM-RETENTION.md` |
| `dod-5015-2.record-declaration-file-plan` | Record declaration & categorisation / file plan (RMA criteria — owned by the records system, not KYE™) | out-of-scope | **constitution\_refs**: `constitution/15-MCP-AND-SDK.md` |
| `dod-5015-2.disposition-transfer` | Disposition & transfer (RMA criteria — owned by the records system / Iron Mountain, not KYE™) | out-of-scope | **constitution\_refs**: `constitution/30-AUDIT-WORM-RETENTION.md` |

Canonical KYE™ surfaces referenced on this page: [KYE Protocol™](https://kyeprotocol.com/).