Start from evidence.
Build toward applications.

An E2B-derived terminal fixture now fixes the first Goal C resource boundary, while the architecture packet orders the semantic compiler work required for large React-shaped applications.

See the direction Execution plan

1Real resource boundary

12Ordered foundation PRs

176/176Tests passing

APPLICATION COMPILER

Keep familiar source.
Generalize the semantics.

EVIDENCE

E2B resource boundary

Terminal handles, generation invalidation, BFCache retention, resume, and discard cleanup remain one explicit unsupported fixture.

DIAGNOSTIC

Fail at the source

Unsupported mutable page refs stop during source analysis instead of reaching the build-time DOM-ref runtime.

SYMBOLS

Resolve before expanding

The first implementation adds one binding index for locals, parameters, imports, captures, globals, and unresolved names.

SEMANTICS

Lower intent once

State operations, component dataflow, resources, and ranges follow stable symbols rather than accumulating exact AST shapes.

ECOSYSTEM

Contain package knowledge

React ecosystem source is classified and normalized behind a compatibility boundary, not copied into a package encyclopedia in core.

AI COST

Measure successful work

Tokens, files, tools, retries, completion time, source retention, browser behavior, and output bytes become explicit product evidence.

UPGRADE

Keep the runtime small. Make the compiler understand more.

$npm install @kudzujs/core@^0.8.27

Start from evidence.Build toward applications.

Keep familiar source.Generalize the semantics.