Choose what can be seen.

Nexus is the shared context-permissions and disclosure layer across Skyzai. It connects a named consumer to the least view needed for a named purpose. It is designed to serve Cortex, APU, Circle, Reality Futures, Agentz, LIQUID, MurMur and permitted external consumers.

Named consumer → purpose → minimum scope → source and revision → expiry → revocation status

Cortex holds the records. Nexus emits a permitted view, never the private store. Derived facts come before raw release.

Use an existing eligible connection and the required consent and grant evidence. Bind each view to its consumer, purpose, permitted scopes, provenance and expiry. Missing, stale or revoked required evidence must stop new disclosure.

People establishes the connection. Identity and Consent bind the principal and consent. Connect issues and verifies grants. Nexus checks the disclosure boundary; it has no signing API. Revocation stops future access where enforced; it cannot recall information already disclosed.

The retained Nexus scope grammar is read-only: nexus.<layer>[.<field>].read.<derived|raw>. Permission to read a view does not authorise record editing, task execution, publishing, signatures, spending, insurance cover or a claim payout. Those controls retain their own accountable owners.

Nexus connects — it does not remember, reason, or sign.

This is the intended common access model. Existing schemas and bounded local proofs do not establish universal runtime enforcement across Skyzai. Each consumer still needs an admitted adapter, current policy and identity/grant evidence, and tests for expiry, revocation and excess scope.

Inspect the technical Nexus contract · The evidence foundation for later insurance

The workspace is now called Cortex. Menexus remains the company, with its own identity and Assure, Insure and Ensure direction. These links retain earlier product bookmarks without treating insurance as a context permission.

• Continue to mission in the current model
• Continue to objectives in the current model
• Continue to strategies in the current model
• Continue to kpis in the current model
• Continue to agents in the current model
• Continue to workflow in the current model
• Continue to purpose in the current model
• Continue to components in the current model
• Continue to capabilities in the current model
• Continue to vmoska in the current model
• Continue to rosetta in the current model
• Continue to ensurance in the current model
• Continue to insurance in the current model
• Continue to assurance in the current model
• Continue to cortex in the current model
• Continue to aia in the current model
• Continue to plan-basis in the current model
• Continue to nexus in the current model
• Continue to next in the current model
• Continue to memory-contract in the current model
• Continue to contexts in the current model