You are here. See how this question connects to other ideas.
Select a node to open its page · Expand to read within the map
One question
explorer: How do you browse AFS resources?
explorer describes a resource-browser subsystem; the runtime must support its expansion and presentation.
Imagine browsing a collection of reports: choose a folder on the left, read a selected report in the middle, and inspect its metadata and actions beside it. explorer describes that combined resource browser. Its src specifies where browsing begins.
This differs from afs-list, which presents a collection of resources. The explorer registry description also includes content preview and an inspection panel. A root pointing to a report collection browses reports. Inspecting interface nodes requires the corresponding interface-resource entry. Interpret that path within its working environment rather than relying on its name alone.
A registered name is not a working control
The runtime must assemble the listing, preview and inspection panels into a usable interface; the registry calls this server-side expansion. Think of it as a composition that the runtime must assemble, rather than assuming every device directly draws a node with that name.
Before using it, verify both that the target runtime supports this composition and that the participant can read the connected resources. Accepting a valid interface description does not establish that those resources loaded successfully. Core vocabulary, device support and resource authority are related but separate checks.
Start with these properties
showMeta controls the metadata inspection panel, such as a report’s type information. showActions controls action buttons. Hiding a button changes presentation; it does not replace authorization when an operation executes.
Registered event names include select and navigate: selecting a resource and moving to a different browsing location are distinct interactions. Their payloads and handling depend on the target implementation.
Read a structural example
From the source registry. This is structural reading material, not a live demo; referenced resources and actions require an application.
{
"id": "file-browser",
"type": "explorer",
"src": "/"
}This minimal example starts browsing at /; it does not explicitly configure panels or event handling. / is the root of the current working environment, not an automatic grant of access to the whole computer.
Check your understanding
What should you inspect to identify the resources an explorer is browsing?
Its connected root path and the namespace and session that give the path meaning.