The questions engineers actually ask.

No any, no casts, exhaustive match, runtime-checked types, and colocated tests that run on every build.

A one-line change is a one-line diff. One canonical layout, nothing repacked.

One name, one declaration form. grep always lands on it.

Yes: import any npm package, keep a hand-written .ts shim where you need one, and import Glyph back into .ts.

No rewrite: the domain core in Glyph, the rest in TypeScript. The output drops into a stock Vite scaffold with zero config.

No. Declare a type, get a validated boundary for free.

glyph gen openapi/zod/dts: committed, greppable code.

First-class JSX, hooks, and exhaustive reducer actions.

A store: a const whose .set/.update are the write-surface.

Because that's where your ecosystem is, and it's why adoption is per-file.

Non-optionality: the language the agent can't config-disable.

Yes: the guarantees are plain engineering wins a human gets directly.

~80% transfers from TS; the compiler's tight feedback closes the rest.

LSP + VS Code extension, and Elm-quality errors with stable codes.

glyph_impact: one verdict per site, from a closed list, with the reason, before you touch the file.

glyph_symbol: a union's variants with the syntax that constructs each, in one call. Eleven tools, each with a glyph query verb.

The diagnostic carries the symbol at fault, the legal alternatives, and what a repairing edit must not break. glyph fix writes the ones the compiler settles on its own.

glyph llms --json emits the diagnostics, the prelude, the stdlib signatures and the tool manual out of the compiler's own tables, and a gate fails when a hand-written copy disagrees.

Readable TS you own, source maps back to your .glyph, and a run that reports what build reports.

Module visibility, interface bounds, defer, a match that works as any value and carries its type, and a standard library that has slice, pad_start, and fold.

Exact decimals and ids, invariants as types, injection as a compile error.

HTML, redirects, response headers, and form posts, without a hand-written server.

await context, a match arm with no value, and a missing mut, reported against your source instead of the emitted TypeScript.

Which field, which rule it broke, the where predicate it violated, and a code to branch on.

io.read_line answers a line as it arrives instead of waiting for stdin to close, so a REPL or a game loop works.

main sets up and returns; the process stays alive while sockets and timers are pending, the same rule Node uses.

Projects pin the compiler exactly, so no release arrives by accident. glyph doctor says one exists; glyph upgrade takes it.

std/bytes is a sequence of octets, with codecs that refuse malformed input instead of skipping it, and HMACs that take a real key.