Reality is the source.
Runtime is the address.
356,782 independently addressable Runtime identities provide a public address layer over bounded Reality references — before ownership, availability, Authority or Delivery are assumed.
A Runtime URL is not the Reality Source itself. Reality is the Source. The Runtime URL is the stable address through which that bounded Reality reference, its evidence, Capability assertions and future Authority path can be resolved.
First establish Source, Address and Capability.
Minimum Authorized Path only becomes meaningful after HSIMC can identify what Reality is being referenced, where its stable Runtime address is, and what Capability value is actually evidenced or still unknown.
Preserve what the address refers to.
Record the reference class, source authority or provenance, identifiers, evidence time and relevant freshness. Stable reference identity does not need to be re-proved on every read; current physical existence or state may still require time-scoped evidence.
Give bounded Reality a stable address.
Runtime ID + canonical URL make the reference independently resolvable. Addressability does not imply ownership, partnership, operator relationship, availability, execution readiness or Authority.
Structure what Reality can contribute.
Capability assertions remain Observed, Inferred or UNKNOWN with Context, Time and Evidence. Capability may exist before Claim; Capability existence still does not imply current availability.
Authority begins after Capability becomes computable.
The 356,782-address namespace is not a catalogue of 356,782 executable services. It is the Reality-to-Runtime substrate on which Capability can be structured and Minimum Authorized Path can later be computed for a real Intent.
Different Reality classes. One Runtime discipline.
The namespace already spans stable reference identities, physical movement nodes, local contexts and on-demand registered buildings. Their semantics remain class-specific; no legal or operational equivalence is implied.
Every Runtime URL must answer seven questions.
The template makes each Runtime page a bounded public compute surface rather than a generic listing page.
At minimum: Reality is the source; Runtime is the address; Capability is the value; Authority is a computable path; Delivery is the outcome.
Country reference, building reference, transit node, airport handoff point, organization, machine, material, service or another bounded Reality role.
For example: not ownership, not an operator relationship, not current availability, not a supplier endorsement, not execution readiness.
Source evidence, Context and assertions in; stable identity and structured Capability state out. Every promotion remains explicit.
Addressable ≠ Available. Claim ≠ Authority. Detection ≠ identity proof. Route ≠ Authority. Capability ≠ permission to execute.
The page must answer a real human problem, not exist only as an internal identifier.
Canonical URL → QR → Copy → Print → NFC where supported. The transferable address remains distinct from consent, authentication and Authority.
Unknown is allowed. False promotion is not.
ADDRESSABLE
A Runtime identity can be public and stable before anyone claims or operates it.
UNKNOWN / EVIDENCED CANDIDATE / STRUCTURED
Capability state depends on evidence. A model inference is not silently promoted to verified execution capability.
UNKNOWN unless time-scoped evidence exists
Availability is a current-state assertion, not an inherited property of the Runtime address.
UNBOUND / NOT COMMITTED by default
Authority requires a path and grant. Delivery requires an accepted Case, Production, Evidence and Human Acceptance.
What does it mean to make Reality addressable?
HSIMC separates the existence of Reality, its Runtime address, its Capability value, its Authority path and its eventual Delivery outcome.