proposed template updates

templates/AMENDMENT_TEMPLATE.md

@@ -332,3 +332,17 @@ _[An indexed list of RPC error codes.]_
   "[ResponseField]": "[example value]"
 }
 ```
+
+## 6. Cross-Feature Considerations
+
+_[All Amendment XLSes should contain a section that discusses how the proposed change interacts with other features on the XRP Ledger, and how conflicts or dependencies should be resolved.]_
+
+A sample list:
+
+- **Deposit Authorization** (Does any transaction involve the transfer of funds from one party to another? If so, Deposit Auth should be integrated into that transaction.)
+- **Batch** (Should any transaction type be excluded from being allowed in a Batch transaction?)
+- **Clawback**
+- **Sponsorship** (Should any ledger entry be excluded from reserve sponsorship? Should any transaction be excluded from fee sponsorship?)
+- **Credentials and Permissioned Domains** (Should this protocol integrate with Permissioned Domains as a permissioning layer?)
+- **Interaction when the submitting account is the Issuer of the particular asset**
+- **Number over or underflows caused by mathematical operations**

templates/XLS_TEMPLATE.md

@@ -60,6 +60,10 @@ _[An optional section that contains a reference/example implementation that peop
 
 _[All XLSes must contain a section that discusses the security implications/considerations relevant to the proposed change. Include information that might be important for security discussions, surfaces risks, and can be used throughout the life-cycle of the proposal. E.g. include security-relevant design decisions, concerns, important discussions, implementation-specific guidance and pitfalls, an outline of threats and risks and how they are being addressed. XLS submissions missing the `Security Considerations` section will be rejected. An XLS cannot proceed to status `Final` without a `Security Considerations` discussion deemed sufficient by the reviewers.]_
 
+## 9. Operational Considerations
+
+_[All XLSes should contain a section that discusses the integration implications of the proposed change, for end users and developers integrating this feature into their applications. This should include information on how the change will be integrated with existing systems, and any potential impact on other XLSes or the overall ecosystem. This section is optional for Meta XLSes.]_
+
 # Appendix _(Optional)_
 
 ## Appendix A: FAQ _(Optional)_