6.2.1 In Scope [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 6.2.1 In Scope ======

[[dido:00-sip-ra:06-specific-requirements-on-proposals:06-2-scope-of-proposals-sought:start|Return to Scope of Proposals Sought]]

The following requirements define the architectural capabilities and abstractions that proposals SHALL address.

  - Proposals SHALL define a platform-independent [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] and its formal [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform Independent Model (PIM)]].
  - Proposals SHALL define the architectural elements, roles, relationships, and interaction constructs that comprise the Reference Architecture.
  - Proposals SHALL distinguish data, [[dido:99_annexes:annex-b-terms-and-definitions:s:structure|structure]], semantics, and interpretation as separable but coordinated architectural concerns.
  - Proposals SHALL define an architectural construct representing the flow of structured information between architectural elements.
  - Proposals SHALL define ordered processing flows composed of modular components connected through governed interaction constructs.
  - Proposals SHALL define explicit attachment points through which structured information enters and exits architectural elements.
  - Proposals SHALL define boundary constructs governing ingress, transformation, and egress of structured information.
  - Proposals SHALL define version-controlled interface contracts governing the exchange of structured information across attachment points.
  - Proposals SHALL define lifecycle governance mechanisms governing structural artifacts.
  - Proposals SHALL define lifecycle governance mechanisms governing semantic artifacts.
  - Proposals SHALL define lifecycle governance mechanisms governing interpretive artifacts.
  - Proposals SHALL define architectural mechanisms supporting reproducible interpretation under version-controlled conditions.
  - Proposals SHALL define architectural mechanisms by which jurisdictions retain control over structural definitions within their operational boundary.
  - Proposals SHALL define architectural mechanisms by which jurisdictions retain control over semantic definitions within their operational boundary.
  - Proposals SHALL define modular integration constructs that support operations across jurisdictional boundaries.
  - Proposals SHALL define modular integration constructs supporting operation across security boundaries.
  - Proposals SHALL define architectural mechanisms enforcing segmentation of information flows based on governance or security constraints.
  - Proposals SHALL define architectural mechanisms separating the data plane and control plane.
  - Proposals SHALL distinguish governance constraints from interface contracts.
  - Proposals SHALL define conformance requirements independently of interface interaction definitions.
  - Proposals SHALL define conformance points supporting inspection and verification independent of implementation technology.
  - Proposals SHALL define architectural mechanisms that separate governance artifact evolution from the execution of the operational processing flow.

----

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