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.

DoD 5015.02-STD: 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: 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

CategoryReqsEnforcedDesignedAdvisoryDeferredCoverage
Access-control decision at the action boundary (authority overlay)22000100%
Audit of the action decision (authority overlay)11000100%
Record declaration & categorisation / file plan (RMA criteria)100000%
Disposition & transfer (RMA criteria)100000%

Every requirement → the KYE™ artefact that enforces it

IDTitleStatusKYE™ enforcement
dod-5015-2.access-control-action-decisionAccess-control at the action boundary: refuse a consequential AI action on a managed record without the required authorityenforcedaudit_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-bindingNamed-authority binding: every consequential action on a managed record is attributable to a named principalenforcedaudit_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-auditAudit of the action decision: an immutable governance audit entry for every consequential action on a managed recordenforcedaudit_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-planRecord declaration & categorisation / file plan (RMA criteria — owned by the records system, not KYE™)out-of-scopeconstitution_refs: constitution/15-MCP-AND-SDK.md
dod-5015-2.disposition-transferDisposition & transfer (RMA criteria — owned by the records system / Iron Mountain, not KYE™)out-of-scopeconstitution_refs: constitution/30-AUDIT-WORM-RETENTION.md

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