SIP-028 — Doctrine, Procedure, and Policy Exclusion

Go to Annex C: Requirements

The proposed Reference Architecture SHALL NOT define operational doctrine, mission procedures, or Domain Policy rules.

Organizations, Jurisdictions, Communities of Interest, and other authorities responsible for a particular operational context establish operational doctrine, mission procedures, and Domain Policy rules.

Including this content in SIP-RA would limit the Reference Architecture to particular missions or organizations and could conflict with authoritative policies and procedures. SIP-RA must define how governed doctrine, procedures, and Policies are identified, represented, distributed, applied, and traced without defining their operational content.

The Submission satisfies this requirement when the proposed Reference Architecture:

1. Avoids defining normative operational doctrine for a particular mission or Domain
2. Avoids prescribing mission-specific procedures or workflows
3. Avoids establishing Domain Policy rules
4. Represents doctrine, procedures, and Policies as governed inputs or external Artifacts
5. Preserves the Authority and provenance associated with those Artifacts
6. Supports different operational contexts using different authoritative rules
7. Distinguishes nonnormative operational examples from the normative architecture
8. Avoids making conformance dependent on a particular organization’s doctrine, procedures, or Policies

This exclusion does not prevent SIP-RA from defining architectural constructs to represent, govern, exchange, select, or apply operational doctrine, mission procedures, or Domain Policies.

A Submission may use representative operational material as a nonnormative example without making that material part of the SIP-RA normative content.