Also, you mentioned integration with notification systems - have you considered webhook support or API integrations so teams could build custom workflows (e.g., automatically creating Jira tickets when an RFC reaches a certain approval threshold, or triggering CI/CD pipeline reviews)?

GDocs might be annoying to track who read the RFC etc. etc. but everyone is familiar with it.

I write RFCs, I share RFCs and your tool seems to require a substantial amount of buy in

- register

- unclear what the writing experience is

- outdated / overloaded UI

The last RFC I wrote was in hackmd (https://hackmd.io/Jjy-afCWS4CAFlHa62anMQ) because

- I wanted Markdown to store the RFC in git eventually

- Google Docs has issues with Markdown rouundtrips

- I didn't want to use git to write with VSCode (although... I actually did. I let CLaude Code write most of the RFC under my guidance, then put it into hackmd for easy sharing)

I hope the feedback helps!

I'm not sure the reason for friction. These are developers, they know how to use git etc, but management prefers google docs I suppose (previous iterations were confluence, then markdown on github).