Section 1.2 Route/Auth Boundary

Authenticated shell boundary

Reserved route — not active authentication. This page defines the future route/auth/backend boundary without creating a working account, server, or customer workspace surface.

Reserved route — not active authentication No login implementation No signup implementation No backend No database No persistence No tenant isolation No customer workspace No public NEXUS runtime
Route Placeholder

Route shape

Public entry
index.html remains the public static entry.
Direct UI Membrane
membrane.html remains the public static membrane context.
Preview workspace
workspace.html remains unauthenticated, browser-side, and non-persistent.
Reserved boundary
auth-boundary.html holds route/auth/backend shape only.
Implementation Boundary

Activation requirements

  • Requires Separate Authorization before real account access.
  • Server-side authorization required before persistence.
  • RLS required before tenant data.
  • Audit contract required before persistent review actions.
Not Active

Current boundary

Auth Boundary Future Authenticated Shell Implementation Boundary Route Placeholder Reserved Boundary Not Active