01 · Permissioned connections
Connect without opening everything.
Nexus is the permission layer within Menexus: one consumer, a defined purpose and a bounded view of the record.
Product in development
Make the permission specific.
The intended access record names the consumer, purpose, allowed operations, relevant objects and expiry. Being in the same network or organization does not automatically unlock memory.
- Who
- Name the person, application or agent receiving access.
- What and why
- Select the records and operations needed for one declared purpose.
- How long
- Set expiry and recheck revocation before delivering more context.
Filter before the model sees it.
The design requires access checks before retrieval and generation, and another check before delivery. Delegation must not widen its parent permission. A model suggestion cannot grant the model access.
Revocation has a real boundary.
Revocation is intended to stop further access. It cannot recall information already delivered. Retention, export and deletion need separate policies for source records and derived copies.
Bounded local permission behavior has been recorded in development sources. This website does not expose a permission service or create grants.