Sovereignty and protocol
The subject retains final judgment. Protocols define what may be called, shared, changed and recovered.
EXTERNAL BODY / ARCHITECTURE
Function, skills, control, information carriers and runtime are different ways to read the same system. Their boundaries need not coincide. The architecture is still being explored; no tool, vendor or automation should quietly become its owner.
The subject retains final judgment. Protocols define what may be called, shared, changed and recovered.
Memory keeps sources and history. An organ names an ongoing function; skills, tools, people and services may contribute to it. A skill is not automatically an organ, nor does an organ have to occupy one directory or process. Trials of assembling organs from skills have not yet produced the intended result.
Interfaces let the system act and be understood. Infrastructure supplies its support; boundaries protect identity and private state. Control also needs a return path: an action’s result must be observable before it can guide the next decision.
A document can hold knowledge, provide an interface and preserve operating history without needing three physical copies. Naming its roles, sources and permitted uses is more useful than forcing it into a single classification tree.