01
Route and render terms
A Route is a file-backed URL module. A render mode controls output and cache behavior. A layout composes shared HTML and inherited metadata around child routes.
02
Boundary terms
A lazy handler is an event chunk loaded after intent. ScopeRef is the tagged server/browser ABI. A binding is a Signal subscription that changes one DOM target.
03
Production terms
An Action is a typed server operation, an adapter maps Fetch-style requests to a host runtime, and a build artifact is generated HTML, CSS, JS, metadata, media, or manifest output.
PRACTICAL LABS
Run this capability.
Each example states the observable output, the boundary that remains your responsibility, and the check that proves the result.
01
Trace one boundary end to end
TextRoute → rendered HTML → data-nx-on / data-nx-bind → ScopeRef payload → lazy chunk or direct binding → browser result- OUTPUT
- The vocabulary maps to observable output rather than abstract lifecycle terms.
- BOUNDARY
- A ScopeRef is public browser data and not a capability, secret store, or request-global context.
- PROVE IT
- Find each link in a built route and its manifest before using the term in a report.
VERIFICATION
Prove the contract.
Use this vocabulary consistently in code reviews, documentation, alerts, release reports, and incident notes.