Live Framework How-To

Use this page when you know the task you want to finish.

Generate A Live App


python3 tools/live-generator.py generate \
  --kind new-app \
  --name hello-live \
  --out build/live-how-to/hello-live

Use lowercase kebab names. The generator refuses unsafe names and refuses to

overwrite files unless --force is set.

1. Put reusable view code under web/components/.

2. Put the checked template shape under web/templates/ when the component has

HTML.

3. Keep domain data in src/.

4. Run:


make live-component-boundary-check
make live-accessibility-check

1. Keep form data validation in a pure helper.

2. Handle submit and change events through the Live form surface.

3. Map invalid input to a form state instead of raising an unstructured error.

4. Run:


make live-form-check

Uploads and streams are stateful. Keep their limits explicit.


make live-uploads-check
make live-streams-check

Use framework auth for login, CSRF, origin checks, token rotation, and session

renewal. Use scopes for tenant, workspace, user, and capability boundaries.


make live-auth-check
make live-scope-check

Use the Live test framework for disconnected render, connected render, click,

submit, change, upload, patch, redirect, reconnect, auth scope, and browser

client behavior:


make live-test-framework-check

Use source-owned observability and bounded dev-server checks:


make live-observability-check
make live-dev-server-check

The observability check proves request, session, event, route, metric, and trace

correlation without leaking secrets.

Production deployment needs release artifacts, CSP evidence, rollback, and

runtime gates. For Kukulkan:


make kukulkan-live-adoption-check
make kukulkan-app-deploy-check

for startup, probes, rollback, logs, and incident handling.