oh my god i just realised the scope of what this project really is about, and quite how ridiculous an amount of work it is going to be to define it properly.
joseph, if i may use you as an example: you want to create hardware, yes? so there are a stack of things that you need to know... but do you need to know what the roles and responsibilities of "recyclers" are wrt the EOMA68 hardware is that you create? well... sort-of... but not directly.
does a "recycling agent" need to know how a particular piece of hardware was designed? well... sort of, only inasmuch as they could really do with the schematics, QA assurance documents from the original manufacturer...
no _wonder_ i'm having diffulty telling people what EOMA68 is about!
gaaaah...