Skip to main content
Knowledge mapDoes shared context mean everyone sees everything?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 and interfaces

One question

Does shared context mean everyone sees everything?

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

  1. Shared resourcesselect and constrain
  2. Projection + access rulespresent permitted view
  3. Observer’s Small World
Relationship sketch · arrows show responsibilities and connections, not a complete protocol sequence.

A report-organizing agent needs the resources relevant to that task and the operations it is allowed to use. That bounded working environment is a Small World. The participant may be an agent, application or process.

Suppose the underlying system contains reports, financial records and contacts. The report task needs only a report. Its view might expose a short address, /data/report, mapped to the underlying resource, with read-only access. A revision task could see the same report with a different operation scope. This is an illustrative configuration, not this website’s current policy.

Selecting resources, mapping addresses and restricting operations constructs a resource projection. A shorter address neither copies the resource nor grants more authority.

Actual access still requires enforcement. Knowing an address does not imply permission to write. A smaller scope also does not make malicious content inside it harmless.

Check your understanding

If an agent knows a path, does it have permission to write?

No. Resolution and authorization answer different questions.

Continue along a learning path