Can I adopt Glyph inside my existing app, or is it all-or-nothing?

Why it matters

Most teams can't rewrite an application, and most of an application doesn't need Glyph. The part that does is the domain core: the rules an AI agent will edit next month and nobody wants silently wrong. Keeping that core in Glyph gives you exhaustive match, no casts, and validated boundaries exactly where they pay, while the React components, the styling, and the infrastructure stay plain TypeScript.

See it

One directory of Glyph sources, compiled into the app, imported by the UI:

src/
  glyph/          # models.glyph, permissions.glyph, analytics.glyph
  generated/      # glyph build --out src/generated src/glyph
  components/     # hand-written React/TSX

// BoardContext.tsx: the app imports compiled Glyph like a local module
import { TaskCard, can_move } from "../generated/models";

const parsed = TaskCard.parse(payload);  // Result, not an exception

Everything the emitted code needs travels with it. Imports are relative, including the bundled standard library, so your project's tsconfig.json and bundler need nothing added: a stock Vite scaffold compiles and bundles the output as-is, and the same files pass a host tsc --strict. Mark what the app imports with pub; a declaration without it is private to its module. This isn't a hypothetical: an outside engineer built a React Kanban board this way, with the RBAC matrix, the analytics formulas, and the status transitions in four Glyph modules under a hand-written React UI.