echelon, it doesn't really sound like you understand the underlying mechanisms of how the human body works.
Without a brain, running an entire body would Require a replacement to that brain, so what you are suggesting is unlikely to be very useful.
Rather, we are already creating scaffolding for individual organs, and we already have technologies that continue to develop that allow us to test against actual human tissues, such that the end-game you point to of 'in situ' testing already is and will continue to be accomplished.
Rather than wasting time and energy attempting to clone an entire human (with all the potential ethical and moral considerations), it is Far easier to simply clone organs, which then allows for direct build/replace scenarios on an 'as needed' basis, And with the full agreement of the source/destination.
Further, as we learn more and more about all the detailed methods and ways that various subsystems, grow, develop, operate, and interact, we can simply create more and more detailed simulations of Any human (or any other creature for that matter) to distinguish proper vs improper function, and investigate and even optimize potential solutions Far more quickly and effectively than spending precious time and other resources.
That is why computational capabilities are and will likely remain our focus moving forward, rather than the arguably cruder and generally Much slower approach which you outlined.
For reference, given the incredibly complex and integrated nature of almost Any living creature, a body without a brain or even without a fully functioning And developed brain would (especially in creatures as complex as humans), in addition to the issues that I already outlined above (along with those raised by others), Also tend to respond Far differently to a fully functional human, thus being of rather limited utility, regardless.
NUM looks to me like a great improvement over the defacto 'status quo' of DNS, Search Engines, and 'Site Sifting' for useful info.
I do have some concerns about the plan to make the owners of various domains that much easier to locate and/or name in lawsuits, as at least here in the US, I could see that info being rather easily abused, along with the initial focus on 'contacts' (see my further comments/concerns below).
That said, given you asked for feedback/suggestions, and what looks to me the focus and high level of usefulness of NUM, especially on streamlining the overall process for 'inter-entity transactions' (whether personal, commercial, or whatever) I believe that a rather useful 'module' (and likely better yet, some number of modules), I would see as Services, Products, and/or Solutions.
Each of those can be seen as either Standard or Custom or perhaps even involve both (ie, a standard Solution for xyz market typically includes abc standard products as well as def custom services or whatever)
This could easily include info about various products, as well as entire 'product lines', along with direct connect to marketing/sales materials and/or contacts, list/actual pricing, specific support resources, whether contacts and/or documentation (manuals) and/or even ways or sites that their organization prefers for handling certain interactions (phone calls, texts, chat, or even say direct (and perhaps non-disclosed) 'click to connect' methods, whereby entering a 'client id' (or having some security certificate) that then perhaps creates a direct connection, or maybe provides a custom 'menu' of options directly available, or whatever, might become possible
Also, given that many companies, groups, governments could also likely use something like this Internally as well, perhaps create the ability to 'federate' the NUM info (both up and down).
Taking that to the next logical step, there could be NUM data/records flagged for different 'audiences'
These 'audience' entries then could be used to auto-magically publish 'internal', 'external', 'vendor', 'client', 'employee', or whatever type records in appropriate places and ways, in NUM, thus helping to maintain appropriate access, security, permissions, etc.
I do really like the option to include public keys as well, as that opens up avenues to directly and easily establish programmatic methods for fully encrypted communications, transactions, file transfers, and whatever else.
In fact, using an organizational public key, along with an employee-designated key (plus whatever other factors) could then be used to instantly create say a Wireguard connection to whichever resources (perhaps including additional NUM/DNS records, data, etc) that that individual has been provided with access to, thus creating a fairly easy way to establish 'Zero Trust', yet fully functional [net]work environments, allowing equal access, no matter where one might happen to be located
That could simultaneously allow for a reduced, if not single, set of security protocols/parameters per organization, and given that simplification effectively tends to increase overall organizational security, similar to how Wireguard is seen as so revolutionary, due to it's simplicity when compared to legacy VPN technologies
That said, I do believe that, additionally, especially for personal contacts/sites/details, and/or organizational units, there really ought to be methods (put) in place to allow for some level of anonymous yet authenticated access, such that NUM doesn't inadvertantly disclose info that ends-up creating yet more 'attack surface' for 'bad actors'
A simple example might be what happens by 'scraping' sites, winnowing down that info, and then publishing it (in clear text).
That would of course be done in an effort to 'help', though I could see that rather easily causing inadvertent complexities, or even outright disasters, especially given how much 'less than skilled' disclosure of info, whether at the individual/family level or at various organizational entities/levels, I have seen happening time and again on Many web-sites world-wide.
Those bits of info Currently tend to be obscured by exactly the nature of how the web has developed (and that NUM seems to be well positioned to address and effectively resolve moving forward) and Yet, at the same time, taking all those juicy bits of info, boiling them all down, and 'canning' them, such that Any script kiddie could then (far more easily And programmatically) utilize all that 'condensed goodness' to then target Anyone or Any group just about Anywhere, simply using NUM's (assuming publicly accessable) data, could well cause some unintended back-lash, if not handled with care.
I do realize that this last one could be an area where there is no simple answer, at least not yet, and I believe I would be remiss if I didn't mention my concerns here as well
Best suited to those with little to no idea what the term robotics even means.
Certainly not what I'd refer to as a 'Master Class'.