2.2 Relationship to SIP-RA [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.
====== 2.2 Relationship to SIP-RA ======

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:02-relationship-to-the-architecture-documents:start | Return to Relationship to the Architecture Documents ]]

SIP-RA gives the project its structured information-processing discipline. It directs the team to decompose information systems into identifiable [[dido:99_annexes:annex-b-terms-and-definitions:r:role|Roles]], responsibilities, structures, interactions, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]-producing behaviours.

This handbook applies that discipline to implementation work. The team should treat [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] directories, generated [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]], [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] implementations, topics, scripts, [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] files, logs, and containers as purposeful implementation Artifacts. Each Artifact should have a clear Role in the Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]].

The handbook does not repeat SIP-RA. Instead, it carries SIP-RA discipline into the Repository, scripts, generated files, Node patterns, topics, logs, and review process. Developers and reviewers should use this handbook to keep implementation Artifacts named, organised, documented, generated, reviewed, and validated in a [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceable]] way.

----

<WRAP centeralign>

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

</WRAP>