docs: the subtitle is what the specification is for

docs/content/_index.md

@@ -1,6 +1,6 @@
 ---
 title: "typescript-as-data"
-description: "Configuration as code, parsed as data."
+description: "A specification for building JSON and YAML compilers from TypeScript."
 ---
 
 ## A policy in YAML and in TypeScript

docs/content/spec/_index.md

@@ -1,6 +1,6 @@
 ---
 title: "The specification"
-description: "The normative text, the reference implementation that implements it, the conformance suite that judges an implementation, and the evidence behind every figure."
+description: "A specification for building JSON and YAML compilers from TypeScript, with the reference implementation, the conformance suite that judges an implementation, and the evidence behind every figure."
 weight: 40
 aliases: ["/introduction/"]
 ---

docs/hugo.toml

@@ -5,7 +5,7 @@ disableKinds = ["taxonomy", "term"]
 
 [params]
   repo = "https://github.com/INTENTIUS/typescript-as-data"
-  description = "Configuration as code, parsed as data."
+  description = "A specification for building JSON and YAML compilers from TypeScript."
 
 # The header's fixed entries. Consumers are not listed here: the header
 # renders a "For your platform" menu from data/consumers.yaml, so a new

paper/draft.md

@@ -1,5 +1,5 @@
 ---
-title: "Configuration as code, parsed as data: a statically evaluable subset of TypeScript with a specified fallback"
+title: "TypeScript as data: a specification for building JSON and YAML compilers, with a specified fallback"
 author: "INTENTIUS"
 date: "Extended draft for comment, September 2026"
 ---