Browse documentation

Explanation

Effects and authority

Typed access, scoped grants and runtime admission serve different roles.

An effect is a typed operation understood by the compiler and runtime. A capability interface or handle provides typed access to it. A scoped grant authorizes use. Runtime admission checks a particular request against its authenticated context and policy.

New to effects? Start with effects, handlers and Septa for examples and a comparison with Unison and OCaml.

A valid type or a capability handle does not itself grant authority.

Check the request

For Checkout to request an Inventory reservation, the system must check the operation and message shape, identify the caller and target, and determine whether the grant permits this request in this scope.

The account context must be trusted. An account identifier in caller-supplied data is not authentication.

For a concrete example, see HTTP requests, grants and execution records. It shows how code requests HTTP, which requests configuration permits and where to inspect recorded attempts.

Keep directions explicit

Inventory’s reply belongs to the reservation request. It does not grant Inventory permission to initiate unrelated operations on Checkout. A later notification or command needs its own contract and authority.

This separation also applies to dependencies: receiving access to one operation must not confer the host’s unrelated permissions.

Separate completion from disclosure

Permission can change after work is accepted. Completing accepted work and later disclosing protected data are separate decisions. Retained history supplies no fresh read authority.

Inspection follows the same rule. A topology or trace can reveal protected information and must respect the viewer’s authority.

Interpret each view

View Describes Does not establish
Declared Interactions in the checked program Permission
Permitted Operations allowed in a named context Execution
Observed Retained execution evidence Complete history or all possible behaviour

Read each view with its code identity, policy context, coverage and dynamic targets. A diagram is not an enforcement mechanism or a proof of complete information flow.

Native hosts retain their own OS authority. Include them in the integration boundary.

Search concepts, guides and reference.