====== 5.1.3 Complete Submissions ====== [[public:00-sip-ra:05-general-requirements-on-proposals:05-1-requirements:start|Return to Requirements]] A complete Submission provides sufficiently precise specification content, assumptions, and context to support independent understanding and implementation. ===== Requirements ===== ^ Requirement ^ Level ^ Statement ^ | [[public:00-sip-ra:99-annexes:annex-c-requirements:gpr-005-precise-and-functionally-complete-submission|GPR-005 — Precise and Functionally Complete Submission]] | Mandatory | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:gpr-005-precise-and-functionally-complete-submission#Statement&noheader&nofooter&noeditbtn}} | | [[public:00-sip-ra:99-annexes:annex-c-requirements:gpr-006-implementation-assumptions-and-context|GPR-006 — Implementation Assumptions and Context]] | Mandatory | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:gpr-006-implementation-assumptions-and-context#Statement&noheader&nofooter&noeditbtn}} | ===== Notes for Editors ===== The requirement identifiers and short titles link to the authoritative requirement records in Annex C. The Statements displayed in this section are transcluded from their corresponding Annex C requirement pages and are not independently maintained copies. Make changes to a Statement or its Requirement Level on its Annex C requirement page. GPR-005 and GPR-006 are mandatory requirements. GPR-005 applies to the completeness and precision of the entire Submission. SIP-042 applies specifically to the completeness of the proposed Reference Architecture specification, while SIP-048 applies specifically to the formal precision of its Platform Independent Model. GPR-006 requires assumptions and contextual information affecting implementation to be stated explicitly rather than left for implementers to infer. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.