demo-tenants

Summary

The two demo tenants every screen draws, and where their data is kept.

Canonical values

Org	Slug	What it is
Norrland	norrland	A small home-goods store. Fully populated. The walked-through example, and what every screen draws.
Kestrel	kestrel	A green-field tenant with nothing captured. Its one project is named blank. What every -empty and -locked state draws.

Branch (Norrland)	Holds
main	every surface
7-add-recs-empty-state	delta #7, mid-flight, one conflict with #140
6-rename-checkout	delta #6, all slices merged

The tables. .context/raw/demo-tenants/<org>/<N>.<table>.js, one file per entity table, numbered in the order a tenant would be seeded: products, branches, users, teams, lifecycle phases, delta types, deltas, slices, events, flags, documents, components, icons, illustrations, personas, route nodes, frames, style token categories, signals. 1.organizations.js and roles.js are global. Each file assigns one array to window.__TRUNK_DATA__.

Nothing reads them. The render scripts that did were removed with the prototype, and there is no app or seeder. They are kept, frozen, in raw/ because they are the source the screens were rendered from and the only full record of the demo content: a future seeder starts from them. A screen is changed by editing its HTML, not a table.

Related

• converted-design-set

Sources

• .context/raw/demo-tenants/