Sources live in Areas. An Area is the one container: it nests freely, it holds Sources, and — once you describe it — it is also the unit an Agent switches on. Organizing the library and preparing it for an Agent are the same act.
Area
Where someone browses.
- Free structure, nests freely
- Holds Sources and other Areas
- Names a subject or collection
- Does not by itself determine permissions
Role
Who owns or may reach governed material.
- Lives within an Axis
- Carries responsibility and visibility
- Has holders
- Must not be recreated as a tree of Areas
An Area with neither description nor instructions is a folder
That is not a second kind of object. An Area with neither a description nor instructions shows as a folder: somewhere to put Sources, invisible to an Agent's routing because there is nothing to route on. Give it a description and it becomes an Area in place, with no move and no migration.
Describing what an Area is for is a later decision, made when you know.
Organize for recognition
Use the words employees already use for subjects, services, and collections. If the same Source belongs in several contexts, reference it rather than making conflicting copies.
Keep public material contained
Sources meant for the public belong in an Area of their own rather than mixed in with internal material. The Area makes the collection explicit, and an explicit collection is one you can audit before a stranger's question can reach it.
Move without changing meaning
Moving a Source changes where people browse for it — and which Agents reach it, because an Agent composes Areas: a Source that leaves an attached Area leaves that Agent's scope. Its owner and its content are unchanged. Review links and human expectations after a large reorganization.
Remove dead structure
Empty Areas and outdated names make the library look bigger than it is. Retire them as the subject changes.