Skip to main content
Knowledge mapWhy expose system capabilities as providers?ArcBlock

You are here. See how this question connects to other ideas.

Select a node to open its page · Expand to read within the map

Knowledge mapFollow a connection. Understand a question.
← AFS

One question

Why expose system capabilities as providers?

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

Make ongoing work inspectable

The proc, registry, observability and UI implementations expose aspects of processes, capability discovery, run records and interface structure. They make parts of the running environment nameable and accessible.

Their resources are not all ordinary documents. A process can end, observations can be paginated, and a UI node can disappear with its session. Lifetime, read cost and authority belong to the interface.

A troubleshooting sequence

If a task no longer updates its display, check whether the corresponding runtime object still exists, inspect its state and failures, then check delivery to the view. This is a method, not a promise of particular paths: discover those in the chosen deployment.

System providers should not become a universal bypass around domain interfaces. Discovering a process or node does not authorize terminating it, reading private logs or editing someone else’s interface.

Check your understanding

Why expose system capabilities as providers?

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

Continue along a learning path