P1-REQ-13-6-005

Return to Part 1 Requirements

Statement

The Conceptual Architecture SHALL distinguish Governance and Authority from the technical mechanisms that support governance.

Source

Part 1, Section 13.6: Separation of Concerns Requirements.

Rationale

Governance and Authority identify decision rights, obligations, control, accountability, and authority relationships. Technical mechanisms support governance through implementation, enforcement, logging, workflow, policy evaluation, access control, or release control, but those mechanisms do not define governance authority.

This requirement prevents technical mechanisms from replacing governed authority, policy accountability, or decision responsibility.

Applies To

This requirement applies to Governance and Authority references within the Conceptual Architecture.

It applies specifically to distinctions between Governance and Authority and:

Policy mechanismsAccess-control mechanismsWorkflow mechanismsLogging mechanismsEnforcement mechanismsRelease mechanismsAudit mechanisms

Verification

Verification SHALL confirm that the Conceptual Architecture distinguishes Governance and Authority from the technical mechanisms that support governance.

Verification activities include review checks confirming that:

Governance and Authority references identify authority, accountability, or decision rightsTechnical mechanisms appear as supporting mechanismsTechnical mechanisms do not define governance authorityLater implementation profiles map mechanisms to governance concerns without redefining them

Traceability

Related source section:

Related requirement identifiers:

Status

Draft

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.