====== SIP-028 — Doctrine, Procedure, and Policy Exclusion ======

[[public:00-sip-ra:99-annexes:annex-c-requirements:start|Go to Annex C: Requirements]]

===== Statement =====

The proposed [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] SHALL NOT define operational doctrine, mission procedures, or [[public:99_annexes:annex-b-terms-and-definitions:d:domain|Domain]] [[public:99_annexes:annex-b-terms-and-definitions:p:policy|Policy]] rules.

===== Rationale =====

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.

===== Evaluation Criteria =====

The Submission satisfies this requirement when the proposed Reference Architecture:

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

===== Referenced By =====

{{backlinks>public:00-sip-ra:99-annexes:annex-c-requirements:sip-028-doctrine-procedure-and-policy-exclusion}}

===== Notes for Editors =====

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.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>