On this page
Mediated Runtime Access
Reader Question
How can a tool or agent inspect and operate on live objects without receiving the process as an unrestricted bag of references?
Short Answer
Nexus is the public policy and registry root for Rift-domain work. A Rift links to
eligible frames and owns current projections plus one room. The room hosts a viewer,
workstation, command surface, events, and memory. Its posture—static, capability, or
codegen—determines which actions are available under compiled frame ACLs.
Access Layers
Viewer reads projection-backed frame, conduit, and spell records.
Workstation holds selected live objects, attributes, methods, and one active target.
Command system mediates room-appropriate runtime operations.
Codegen system validates, builds a bounded namespace, compiles, and executes only in a codegen room.
Rift gates and frame ACLs coordinate in-flight operations and refresh authority.
Room Postures
Room |
Intended authority |
|---|---|
Static |
Read-only live introspection and reuse-only surfaces |
Capability |
Broader manual discovery, activation, and topology operations |
Codegen |
Selected runtime helpers plus validated code execution |
Why This Design Is Strong
Authority is represented as a room and projection contract rather than an informal set of objects handed to an operator. The same live world can support different users with different compiled surfaces.
Tradeoffs
Bounded access requires ACL families, projection refresh, gates, and room configuration. That cost prevents the common alternative: one all-or-nothing introspection/tooling API whose caller can see or mutate everything.
Where to Go Next
Source entry points: