Named resources
Paths
A path gives a task a stable way to refer to a resource instead of relying on an implicit location or a pasted instruction.
An agent needs a world it can name
AFS (Agentic File System) turns the files, services, and active work relevant to a task into an inspectable resource view. Instead of handing an agent an undifferentiated machine or a pile of APIs, it gives the task a world with names and boundaries.
A working view
AFS uses paths, mounts, and projections to describe what a task can see. Those are different parts of one resource view, not three names for the same permission system.
One view, not one machine
Mounts and projections
A mount connects a resource into the view; a projection presents the part relevant to an agent, application, or process. Permission to read, change, or execute remains a rule of the system using that view.
Local FS
A local project is a concrete place to see the abstraction at work.
Developer example
Mount a directory you chose
The AIGNE Local FS example connects a local directory to AFS so an agent can find, read, and manage files within the declared scope.
Developer example
Local FS example
The documentation starts with mounting a directory and using file tools. It is a starting point, not a default grant of access to a whole machine.
Small World
The published Small World explanation gives the broader idea behind a projected resource view.