Live Package Migration

This page explains how to move from direct lower-level Live package imports to

the unified 0x0 Live framework namespace.

Unified Import

New app code should import the framework surface:

(↥ "frameworks/live/runtime.0x0")

The framework namespace wraps the implemented Live package family without

removing the lower-level packages.

Package Map

The source-owned package map is frameworks/live/package-map.tsv. It records

the package id, status, source path, kind, owner surface, and evidence gate for

each framework package.

Compatibility

Existing lower-level imports remain valid. Move an app to the unified import

when the app needs endpoint, router, auth, scopes, templates, components,

client bridge, release gates, deployment, and test evidence in one framework

surface.

Do not change public behavior while moving imports. Run the same app gates

before and after the change.

Migration Steps

1. Add the unified framework import in the web-facing module.

2. Keep pure domain imports under src/.

3. Move route and template ownership under the Live app directory shape.

4. Replace direct test fixtures with framework test helpers under test/.

5. Run the framework gates for the surfaces touched.

6. Update release evidence and public docs in the same change.

Release Evidence

Use these gates for migration evidence:

make live-framework-surface-check
make live-framework-app-shape-check
make live-test-framework-check
make live-security-check
make live-learning-check

Kukulkan additionally uses:

make kukulkan-live-adoption-check