The app framework built for the second change. And the fiftieth.

A single turborepo on the committed 2026 stack.

The stack is settled capital, carried across ten generations. Changing one piece is a decision record with a migration plan — never a fresh repo.

Declare one table. Grow a whole admin surface.

A Drizzle column wrapped in withMeta is the seed. Sprout reads the metadata and derives the entire CRUD surface at runtime — no per-entity code, no scaffolding to maintain.

import { boolean, pgEnum, pgTable, text, uuid } from 'drizzle-orm/pg-core'
import { withMeta } from '@maxstack/core'

export const priorityEnum = pgEnum('priority', ['low', 'medium', 'high'])

export const task = pgTable('task', {
  id: uuid('id').primaryKey().defaultRandom(),

  title: withMeta(text('title'), {
    label: 'Title',
    placeholder: 'What needs doing?',
    minLength: 1, maxLength: 200,
    required: true,
  }).notNull(),

  done: withMeta(boolean('done'), { label: 'Done' })
    .notNull().default(false),

  priority: withMeta(priorityEnum('priority'), { label: 'Priority' })
    .notNull().default('medium'),
})
// that's the whole definition — no controllers, no forms.

Always reach for the lowest rung that expresses the change.

Every change goes up an explicit ladder — cheaper rungs absorb more, and regeneration stays safe by construction. The weight is what the maintainer paid; the platform's job is to keep changes on the low rungs.

The invariants that make it safe: additive-only spec-ops + additive DDL · manual rows survive regeneration · generators ground only on accepted entities · the manifest-checked never-clobber writer. Every change ends with maxstack validate.

One typed spec, a handful of verbs.

A project is its own directory and lives anywhere on disk. The authoring verbs are standalone; dev borrows the runtime, build vendors it in.

Standard features as tested, upgradeable bundles.

A bundle bundles runtime, its own eval artifacts, and prerequisites — installed through the exact validated spec-op path an agent uses. Versioned, with upgrade codemods. No copy-paste starter rot.

The north star is change-safety — and it's measured.

Time-to-Nth-safe-change: the effort and success rate of landing a change to an already-live app with the regeneration-safety suite still 100% green. This is the one number the whole platform exists to move.

Read the framework, not just the pitch.

Everything the maintainer needs — setup, the change ladder, the workbench, the metrics protocol, the deploy runbook.