Frontend compiler

Development

Raster

Typed TSX -> TSX*

Compile typed React applications from TSX.

Scope

What it does.

Raster starts with real TypeScript and TSX. It checks routes, data access, commands, design-system use, and permissions against the DOSS model, then emits TSX*, typed clients, plans, and source maps. React remains the runtime.

Raster / System architecture

TypeScript in. A complete React application out.

Raster compiles only the relationships that cross DOSS boundaries. React keeps rendering, React Router keeps routing, the query client keeps read state, and ZFlow keeps durable work.

control

execution

state

Evidence

Canonical source

page PurchaseOrder

layout: DetailWorkspace

query: Procurement.po

command: approvePO

gate: canApprove

slot.body: POLines

Ordinary pure TSX remains TSX. Every relationship that fetches, mutates, authorizes, routes, or establishes placement identity is explicit.

RasterCompiler passes

01Parse TypeScript AST

02Resolve Configbase + Interfaces

03Validate policy, bindings, identity

04Normalize compiler-owned IR

05Typecheck generated output

Synchronized generated graph

TSX*

Expanded routes, gates, bindings, and stable identities.

Module clients

Typed Query and Command adapters from pinned interfaces.

PagePlan

Static Explain graph, placements, dependencies, and policy.

Diagnostics

Schemas, source maps, and authored-source correlation.

Browser runtime ownership - Raster adapts, it does not replace

React

Rendering + component state

React Router

Page mounting + URL state

Query client

Remote reads + invalidation

ZFlow

Durable Commands + progress

Outputs

Typesafe React App

Inspectable PagePlan

Policy-safe query and command bindings

What feeds back

Diagnostics, Explain IDs, command results, and source maps point back to the authored line.

Responsibilities

What it owns

Write real TSX

Use TypeScript, React, layouts, components, Queries, and Commands.

Check the edges

Validate routes, slots, data bindings, access gates, and module boundaries before build.

Regenerate the output

TSX*, clients, PagePlans, schemas, and source maps always come from source.

Keep React

Raster connects authorization, queries, commands, and Explain without replacing React or its router.

Dependencies

What it connects to

Raster calls these products and services directly.

ZSL ZebraDBZFlowTetrisUI

DOSS Labs

Talk to us about Raster.

Get in touch

DOSS

Careers Contact