TypeGlish 0.2.2: 'the' names an object, and the docs go live

TL;DR 0.2.2 gives TypeGlish a definite-article object system: write The shop is a bakery and shop is a real object you can point at with @{shop}. It also puts the full docs online at typeglish.dev/docs, generated from the language's own source of truth and organized around Writing, Compiling, Testing, and Optimizing. Upgrade with npm i -D typeglish@latest.

0.2.1 was plumbing; 0.2.2 moves the language again and gives it a home to be read in. The headline is a grammar feature that sounds trivial and is not: the word "the" now carries meaning to the compiler. Alongside it, the reference that used to live only inside typeglish reference is now a browsable site at typeglish.dev/docs. Upgrade with npm i -D typeglish@latest, or run it with no install at all: npx typeglish@latest check **/*.tg. Here is what shipped.

§1"the" names an object

Until now, to introduce a thing your prompt could refer to later, you wrote it as a bare capitalized name: Shop IS a bakery binds shop. That works, but it is not how anyone writes English. You do not say "shop is a bakery"; you say "the shop is a bakery." 0.2.2 makes that sentence mean exactly what it reads as. In a subject position, the definite article declares an object: The shop is a bakery names exactly one shop and binds it, the very same object the bare name would have bound. It is the definite article doing the job it does in English - pointing at one specific thing - now wired into the type system.

That matters because references stop fighting your prose. A support prompt reads the way you would brief a new hire, and the objects you name in passing are real, checkable symbols. Here is a whole, honest prompt that leans on "the" and compiles clean:

The bakery is your workplace.
You greet every customer by name.
You never quote a price for anything the bakery sells.
WHEN a customer asks for the manager THEN escalate to a human.

Because a "the"-declared object is a first-class declaration, it plugs into everything the compiler already does with symbols - including the pointer plane. Point at it with @{shop} and the value inlines at compile:

The shop is a bakery.
You work the morning shift at @{shop}.

§2The docs go live at typeglish.dev/docs

The language reference has always shipped in the box - typeglish reference prints it, written for an agent to read first. 0.2.2 gives it a second front door: a real documentation site at typeglish.dev/docs, and the Docs link in the header now goes somewhere. Four things landed together to make it one.

First, it is generated from the source of truth, not hand-written - the same lexicon and layer definitions the compiler runs are what render the pages, so the docs cannot drift from the language the way a maintained-by-hand site does. Second, it is served on a subpath, /docs, rather than a separate subdomain, so it sits under the same origin as the app and the blog. Third, moving around is client-side navigated: following a link swaps the content without a full-page reload, so the reference reads like an app instead of a stack of static pages. Fourth, it is organized around a tab bar with four sections that mirror what you actually do with a prompt: Writing, Compiling, Testing, and Optimizing - the same arc as the CLI workflow, from authoring a .tg to scoring it.

The Writing section is the one that most repays a visit: its reference is generated per language layer, straight from the compiler's LAYERS definition, so every operator, sigil, and declaration form is documented from the same structure the checker enforces. If you have been learning TypeGlish from blog posts and --explain, this is the map that ties it together. It pairs well with our field guide on where the rules go and the eight prompting rules that survive production.

§3The smaller changes

The rest of 0.2.2 is foundation work - the kind that does not change what you write but makes the thing that reads it more trustworthy.

• The layer architecture, mechanically enforced. The compiler was refactored to one file per semantic layer, with the split enforced by tooling rather than convention. It changes no behavior you can see from a .tg file, but it is what keeps each layer of the language - lexicon, types, quantifiers, conditionals - honest as the language grows, and it is what makes the per-layer docs above generatable in the first place.
• Absolute /docs asset paths. A bugfix so the docs site loads its stylesheets and scripts from absolute /docs paths, which is what makes client-side navigation between docs pages resolve correctly no matter how deep the current page sits.