Understandable first
Six products, one shopping list, and one fake checkout. No authentication, backend, persistence, or real payment ambiguity.
Application experiment
Product proving ground
Lastro
The app-level experiment for learning whether the Lilscript stack can produce a small, understandable, accessible web experience—not another compiler hidden in the stack.
Why it exists
A real interface exposes problems tiny fixtures miss
Parcel Market exercises loading, repeated data, derived totals, quantity updates, multi-screen state, form interaction, and reload behavior in one deliberately small app.
Usable without a mouse
Semantic regions, keyboard focus, visible outlines, live status announcements, explicit button names, and reduced-motion behavior.
Lilscript remains central
The adjacent POC keeps listings, prices, quantities, and screen transitions in main.lil, with only a narrow typed browser host.
Implemented path
What powers the experiment
- Lastroproduct constraints and Parcel Market experience
- Lilastropage shell and Lilscript entry selection
- Lilscriptapplication data, behavior, and generated markup
- Lilpackmodule graph, HMR, and production delivery
Accessible demo
Parcel Market is available here
The hosted example starts with an announced skeleton state, then exposes six listings. Add multiple quantities, remove them one at a time, clear the list, enter the fake checkout, and finish on a local success screen.
Demo contract
No details are transmitted or stored. The payment form is intentionally prefilled with test data and clearly labeled as fake.
Current definition
Lastro owns
- Application-level experience and constraints
- The reference marketplace flow
- Accessibility and interaction acceptance criteria
- A realistic target for language and bundler work
It does not own
Separate responsibilities
.lilastroparsing—that is Lilastro- Lilscript compilation—that is the compiler core
- Bundling and HMR—that is Lilpack
- A general component runtime—that is a separate experiment such as SolidLil