I agree. For SocialHub I proposed in the past processes along 3 tracks. I guess with 3 different speeds to them, and decreasing levels of formality that are needed:
- Open standards track. Incorporating FEP’s and such, create next-version AP et al specs.
- Fediverse Enhancement Proposals. Mechanisms that are essential for the ‘plumbing’ level of interoperability.
- Domain-specific vocab extensions. Going into all kinds of directions while building upon 1) and 2)
Track 1) and 2) exist, but have stalled. 3) doesn’t exist other than in numerous fedi app codebases.
Update: Note that we have some informal agreement to have a FEDERATION.md and some projects have that. It is a form of documenting track 3), but not easy to find. There’s a possible Improvement to FEDERATION.md convention: Murmurations, and various discussions about capability discovery which in theory need not be a very complex thing if only referring to specific vocab extensions that are supported.