The reader itself should accept multiple reader options:

• path => the path to the definitions
• features => list of features that should be loaded (optional)
• panic/skip => decide if the reader should panic when a definition can't be parsed or just skip it (optional)
• version => only accept a definition with a specific version (optional)

Then the reader should understand the following structure:

<root>
 <feature> (folder)
   <flow_type> (folder)
   <data_type> (folder)
   <functions> (folder)
 <feature> (folder)
   <flow_type> (folder)
   <data_type> (folder)
   <functions> (folder)

Inside of each flow_type/data_type or functions folder sub folders can exsist.
A readable definition always ends with .proto.json