A world of resources you can operate on.

AFS gives a task a named, inspectable view of the resources it can work with.

A path identifies a resource within a namespace, so operations can refer to it explicitly.

A provider implements resource operations; a mount places that provider in a namespace.

Naming a resource is useful only when consumers can understand what operations on it mean.

A Small World presents the resources relevant to one observer, rather than exposing the whole system.

An entry path and the resource’s original location are different things.

Location, supported operations and caller authority are separate questions.

Reading the same address and receiving changes are separate steps.

A shared address does not decide how stale edits are handled.

Finding relevant content differs from selecting records by explicit conditions.

Missing, unsupported, denied and conflicting operations need different responses.

A local path can represent a remote service without removing network and authority boundaries.

Connection or registration direction changes; authority does not automatically reverse.

Common names and operations let tools work across resource implementations.

A participant can assemble a resource view that includes remote services.

Providers use their own relative paths; the dispatcher restores the mount prefix.

Check declared shared contracts, not merely whether a demonstration runs.

Success-only examples miss over-broad access, swallowed errors and lost updates.

Classify resources and responsibilities before repository directories.

Runtime state and capabilities can have structured entry points with their own lifetimes.

Common operations preserve differences in location, structure and persistence.

Permissions, latency and side effects remain part of the service contract.

Begin with one explicit resource and its path contract before adding operations.

An action needs discoverable arguments, effects and failures as well as a handler.

Mount a report at /work and check it with shared tests and an actual read.

Discover the resource, inspect its explanation, then use supported operations.

Prompts orient the caller; explain supplies guidance for a particular path.

MCP supplies the connection contract; AFS supplies the resource environment and semantics.

Exposing AFS to MCP clients differs from mounting an MCP server into AFS.

Observe discovery, reads, operation choice and result verification separately.