Minimum Authorized Path
Capability may be visible and still be unreachable. HSIMC computes the minimum valid path by which a Capability can become legitimately accessible to a Runtime inside an acceptable Reality envelope.
Connection is not Authority
A short social path, a payment, an ownership claim, a job title or a personal relationship may reduce friction, but none of them automatically creates permission to use a real-world Capability. The valid path must satisfy the required identity, scope, consent, compliance, context and evidence conditions.
The compute problem
Given an Intent, a source Runtime, a target Capability, one or more candidate Runtimes and an Authority Graph, HSIMC searches the feasible paths that satisfy mandatory constraints and then minimizes the cost of access.
Hard constraints
Identity, legitimate authority source, scope, Context, consent, compliance and any required evidence.
Path costs
Time, money, evidence burden, relationship friction, language, jurisdiction, travel, coordination, irreversibility and recovery.
Why a Runtime is required
“I want to use this capability” is not enough information to compute access. HSIMC needs a bounded Runtime containing the Intent, identity, Context, existing capability, acceptable Reality, time and evidence state. The same meeting room or machine can have a different Minimum Authorized Path for different Runtimes.
Public graph, private authority graph
HSIMC can make the existence of capability publicly discoverable without publishing private relationship edges, personal contact networks, trust evidence or internal path weights. Public users may see that an authorized path is potentially reachable; the sensitive graph used to compute that path remains governed infrastructure.
Minimum Authorized Path is therefore not a directory feature. It is the computation that converts visible capability into legitimately accessible capability.