Getting Started

This section documents the source-level Generative UI proof, not the separately published Tessera Studio product. There is currently no tessera-agent CLI or remote shadcn registry for this component system. The first successful workflow here is to verify the final Generative UI foundation and inspect the data-agent components that exercise it.

Prerequisites

• Bun 1.3.14 or later
• A browser supported by Next.js 16 when running the documentation site

A database and model key are not required for deterministic architecture, contract, renderer, and fixture tests.

Run the proof gates

From the repository root:

bun install
bun run check:naming
bun run check:boundaries
bun run typecheck
bun run test
bun run build

These commands verify package boundaries, browser/server separation, canonical protocol behavior, Component Contracts, renderer coverage, and the single React render path.

Open the Tessera Agent documentation

bun --cwd apps/docs dev

Open the local URL printed by Next.js, then start with the Generative UI architecture, the data-agent proof gates, and the current component catalog.

The optional documentation playground reads OPENROUTER_API_KEY. It currently streams text only and is not evidence that the trusted Generative UI pipeline is connected. The product proof must use the real chain:

SurfaceEventStream -> SurfaceController -> GenerativeSurface -> RendererRegistry

Definition of success

Success is not merely rendering valid component JSON. Tessera Agent must turn a governed query resource into useful metric, chart, table, filter, query-detail, and explanatory compositions while keeping query rows outside model proposals, canonical documents, transport history, and ordinary logs.

Do not start a separate Open Generative product from these instructions. That extraction begins only after the Tessera Agent proof gates pass.