Should we organize the content in a way that it somehow reflect the content of the `spec` under the CometBFT repository? It would be something like (only directories are printed): ``` $ tree -d spec -I draft -I img spec ├── abci ├── blockchain ├── consensus │ ├── consensus-paper │ ├── light-client │ │ └── assets │ └── proposer-based-timestamp │ └── tla ├── core ├── ivy-proofs │ └── output ├── light-client │ ├── accountability │ │ └── results │ ├── assets │ ├── attacks │ ├── detection │ ├── supervisor │ └── verification ├── p2p │ ├── messages │ ├── quint │ ├── reactor │ └── v0.34 └── rpc ``` The proposal is not to *restrict* to this directory structure, but to use it as a base.
Should we organize the content in a way that it somehow reflect the content of the
specunder the CometBFT repository?It would be something like (only directories are printed):
The proposal is not to restrict to this directory structure, but to use it as a base.