You could include “either x or y or z…” specifications in the unified documentation.
So “Either soft deletion is to be disabled as by default in which case [explain standard behavior], or it is to be enabled by [yadda yadda]…”
The single document is searchable and cross-referenced internally, making it better in many cases.
silverpill@mitra.social 1 week ago
By separating core protocol requirements and optional features.
The guide has a section titled "Protocol features":
https://codeberg.org/ap-next/ap-next/src/commit/f1ee497085f56cde9860b9417eba8cd05cd1522a/guide.md#protocol-features
This is a place where information about optional features is collected, and soft deletion FEP could be mentioned there. A formal specification could be structured in a similar way.