GITBOOK-1028: Gemma's Jul 15 changes technical policy

Author: GemmaDakin

legal/policies-and-conditions/intersect-administration-policies/technical-review-policy.md

@@ -56,6 +56,10 @@ _Updated on 4th July 2025_
 * Any deliverable which affects crypto primitives, ledger, or consensus rules must seek prior agreement on technical audit and testing prior to commencement of any deliverable. 
 * Because requirements for new features may not be able to be defined in this policy in advance, any other reasonable requirement for technical testing, auditing, or security review must be met. 
 
+_Examples_
+
+<table><thead><tr><th width="378" valign="top">Acceptable</th><th width="379" valign="top">Unacceptable</th></tr></thead><tbody><tr><td valign="top"><p><strong>Minor Update/Merge to Core Code Repository:</strong></p><p><br></p><p>Full adherence to any repository specific documentation (example here: <a href="https://github.com/IntersectMBO/cardano-node">https://github.com/IntersectMBO/cardano-node</a>) </p><p></p><p>Full adherence to repository review and merge process</p><p></p><p>Sign off from Repository Maintainers/Owners.</p></td><td valign="top"><p><strong>Minor Update/Merge to Core Code Repository:</strong></p><p><br></p><p>Uncommented code, or code which does not adhere to the policies or practices defined within the repository in question</p><p></p><p>Non-adherence or violation of any release or releasing markdown(md) requirements or similar. <br></p><p>Vague or ambiguous statements or testing which cannot be understood, verified or easily replicated.</p></td></tr><tr><td valign="top"><p><strong>Ledger Feature Release:</strong><br></p><p>Full Node Release Testing (here: <a href="https://tests.cardano.intersectmbo.org/readme.html">https://tests.cardano.intersectmbo.org/readme.html</a>) </p><p></p><p>Full adherence to any repository specific documentation (example here: <a href="https://github.com/IntersectMBO/cardano-node">https://github.com/IntersectMBO/cardano-node</a>)<br></p><p>CICD Sign off from:</p><ul><li>Test Engineer</li></ul><ul><li>Performance Engineer<br>Site Reliability Engineer</li><li>Release Engineer</li></ul></td><td valign="top"><p><strong>Ledger Feature Release:</strong></p><p></p><p>Uncommented code, or code which does not adhere to the policies or practices defined within the repository in question</p><p></p><p>Non-adherence or violation of any release or releasing markdown(md) requirements or similar. <br></p><p>Vague or ambiguous statements or testing which cannot be understood, verified or easily replicated.</p></td></tr><tr><td valign="top"><p><strong>Full Node Version Release:</strong><br></p><p>Full Node Release Testing (here: <a href="https://tests.cardano.intersectmbo.org/readme.html">https://tests.cardano.intersectmbo.org/readme.html</a>) </p><p></p><p>Full adherence to any repository specific documentation (example here: <a href="https://github.com/IntersectMBO/cardano-node">https://github.com/IntersectMBO/cardano-node</a>)<br></p><p>CICD Sign off from:</p><ul><li>Test Engineer</li><li>Performance Engineer<br>Site Reliability Engineer</li><li>Release Engineer</li></ul></td><td valign="top"><p><strong>Full Node Version Release:</strong><br></p><p>Uncommented code, or code which does not adhere to the policies or practices defined within the repository in question</p><p></p><p>Non-adherence or violation of any release or releasing markdown(md) requirements or similar. </p><p></p><p>Non-adherence, or evidence of completion, of cardano-node-test. Or public release of results.</p><p><br></p></td></tr><tr><td valign="top"><p><strong>DApp Feature or Release:</strong></p><p></p><p>Advised to follow provided delivery assurance best practice for required technical review and or audits where required.<br></p><p>Ultimately the vendor should want to demonstrate safe, secure applications and code as this is likely to increase utilization and ultimately delivery better benefit to the community. </p><p></p><p>Vendors are encouraged to demonstrate progress and incorporate community throughout development lifecycles, through prototyping, AMAs/Q&#x26;A as well as other live sessions.<br></p></td><td valign="top"><p><strong>DApp Feature or Release:</strong></p><p></p><p>Features or applications released with no prior community engagement. </p><p></p><p>Features or applications where no feedback loops are present or available for the community. <br></p><p>Features or applications where no testing or development can be seen on testnets or through prototyping. </p><p></p><p>Ultimately Intersect cannot force a vendor to undertake certain actions, but as an Administrator we can make it clear where developers and vendors have taken all due diligence and care to develop safe, secure applications for the betterment of the ecosystem.</p></td></tr></tbody></table>
+
 **12. Roles and responsibilities:**
 
 **Intersect (administrator)**&#x20;