{ "model": { "rank": 2880, "code": "thing-q5310", "model_id": "vr.tr.latex", "name": "LaTeX", "purpose": "Enable an AI agent to recognise a LaTeX document system, assess whether its sources can produce the intended document reliably, and decide which editing, compilation and distribution actions are appropriate.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.MED", "industry": "", "version": "", "url": "/models/thing/q5310/", "tier": 2, "score": 95, "payload": { "layer": "wikidata", "aliases": [], "aliasCount": 0, "merged": 0, "knownIn": 95, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": "vr.tr.latex", "source": { "dataset": "wikidata", "item": "Q5310", "url": "https://www.wikidata.org/wiki/Q5310", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T13:25:11Z", "providers": [ "Codex", "Grok" ], "missingProviders": [], "pass": 2, "cost": { "grok": { "usd": 0.0048824, "turns": 1, "seconds": 69.7, "error": null }, "codex": { "seconds": 77.6, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a07c0a-221d-7ad2-9242-7693490ae3f2\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: LaTeX\nRegistry id: vr.tr.latex\nPlane / domain: INF / INF.MED\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\nA Vercy model" } } }, "metaModel": { "id": "THING-Q5310", "registryId": "vr.tr.latex", "name": "LaTeX", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.MED" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q5310/", "model": { "registry_id": "vr.tr.latex", "name": "LaTeX", "purpose": "Enable an AI agent to recognise a LaTeX document system, assess whether its sources can produce the intended document reliably, and decide which editing, compilation and distribution actions are appropriate.", "definition": "LaTeX is a document-preparation system and macro package for TeX that lets authors describe the logical structure of a document so a typesetting engine can produce high-quality, consistently formatted output, especially for mathematics, scientific papers, and other structured publications.", "scope_statement": "This model owns LaTeX as a document preparation system and the LaTeX-specific properties of its source projects: document structure, macros, classes, packages, compilation requirements and resulting typeset behaviour.", "in_scope": [ "Identification of LaTeX source and its intended document entry points", "Document classes, packages, custom macros and their interactions", "Semantic document structure, mathematical notation and cross-references", "Engine requirements, bibliography and indexing workflows, and build dependencies", "Compilation state, typesetting quality and source-to-output traceability", "LaTeX-specific constraints on safe execution, collaboration and submission" ], "out_of_scope": [ "TeX engine internals and general programming-language semantics", "The correctness or evidential quality of the document's subject matter", "PDF format internals and general PDF editing", "General version-control, storage and software supply-chain management", "Independent models of fonts, images, datasets and other embedded assets", "Publisher business processes and editorial decisions" ], "distinguishing_features": [ "A .tex extension alone is insufficient: recognition requires evidence that the source targets the LaTeX format, such as document-class selection and a LaTeX document environment, or depends on a parent project that does.", "LaTeX source expresses document structure and typesetting instructions through commands and environments; it is distinguishable from plain TeX by its reliance on LaTeX conventions and interfaces.", "A rendered PDF is an output, not sufficient evidence of an available LaTeX source project or its build requirements.", "A TeX distribution supplies engines and packages, while LaTeX is the document preparation system used through those components; the installed distribution and the document's required format must be distinguished.", "Markdown or other source converted into LaTeX has a separate authoring origin; generated LaTeX must be distinguished from the source an agent is expected to edit." ], "characteristics": [ { "name": "Source role", "kind": "category", "unit_or_values": "document entry point | included fragment | class | package | generated source", "why_it_matters": "Determines whether a file should be compiled directly, edited locally or changed through its upstream generator." }, { "name": "Document class", "kind": "relation", "unit_or_values": "class name, options, origin and required version when known", "why_it_matters": "Establishes document conventions and constrains compatible layout changes." }, { "name": "Required compilation engine", "kind": "category", "unit_or_values": "pdfTeX | XeTeX | LuaTeX | other specified engine | unresolved", "why_it_matters": "Engine choice affects command support, font handling and package compatibility." }, { "name": "Dependency resolution", "kind": "state", "unit_or_values": "resolved | missing | conflicting | unverified", "why_it_matters": "A source tree cannot be judged buildable without its required classes, packages and external inputs." }, { "name": "Build convergence", "kind": "state", "unit_or_values": "not attempted | failed | rerun required | converged under recorded checks", "why_it_matters": "A successful engine invocation may still leave references, citations or generated lists incomplete." }, { "name": "Unresolved references and citations", "kind": "measurement", "unit_or_values": "count from the latest identified build", "why_it_matters": "Exposes broken links between document elements and incomplete bibliography processing." }, { "name": "Typesetting diagnostics", "kind": "measurement", "unit_or_values": "counts of overfull and underfull boxes, with locations and review status", "why_it_matters": "Identifies layout areas requiring inspection without treating every warning as an output defect." }, { "name": "External execution requirement", "kind": "state", "unit_or_values": "none identified | restricted execution required | unrestricted execution required | unknown", "why_it_matters": "Determines whether the intended build fits the available execution permissions." }, { "name": "Output freshness", "kind": "state", "unit_or_values": "matches recorded inputs | stale | provenance unknown", "why_it_matters": "Prevents an agent from judging or delivering output produced from an earlier source state." } ], "affordances": [ "Identify the document entry point and distinguish authored files from generated intermediates.", "Inspect and revise document structure, mathematical markup and custom macros while respecting class and package interfaces.", "Resolve build requirements and run an authorised compilation workflow.", "Diagnose compilation errors, unresolved references and typesetting defects.", "Assess whether generated output satisfies the specified layout, accessibility and submission requirements.", "Prepare a source handoff with the dependencies and build instructions needed to reproduce the document." ] }, "sources": [ { "id": "src-latex-project", "title": "LaTeX - A document preparation system", "url": "https://www.latex-project.org/", "what_it_supports": "Official project definition of LaTeX as a TeX macro package, current LaTeX2e kernel, and LaTeX3/expl3 work.", "url_status": "live" }, { "id": "src-ctan-latex", "title": "latex - A TeX macro package that defines LaTeX", "url": "https://ctan.org/pkg/latex", "what_it_supports": "Canonical package identity on CTAN, LaTeX2e as current version, historical 2.09, and relationship to TeX.", "url_status": "live" }, { "id": "src-wikidata-q5310", "title": "LaTeX (Q5310)", "url": "https://www.wikidata.org/wiki/Q5310", "what_it_supports": "Stable identifiers (Wikidata Q5310, Freebase, Library of Congress, GND) and classification as a document markup language / typesetting system.", "url_status": "live" }, { "id": "src-iso32000", "title": "ISO 32000-2:2020 Document management - Portable document format - Part 2: PDF 2.0", "url": "https://www.iso.org/standard/75839.html", "what_it_supports": "The principal interchange standard for the PDF files LaTeX engines commonly emit; not a LaTeX specification itself.", "url_status": "blocked" } ], "structure": { "bundles": [ { "id": "source-identity-and-boundaries", "name": "Source identity and boundaries", "description": "Establish what constitutes the LaTeX project and which files control the intended document.", "rationale": "LaTeX projects can contain multiple documents, reusable extensions and generated fragments whose editing and compilation roles differ.", "layers": [ { "id": "document-entry-points", "name": "Document entry points", "description": "Recognise the LaTeX format and locate compilable document roots.", "findings": [ { "id": "latex-format-and-root-evidence", "name": "LaTeX format and root evidence", "description": "Record the evidence that a source targets LaTeX and identify the root used for each intended output.", "questions": [ { "text": "Which commands, environments or parent-project declarations establish that this source targets LaTeX rather than plain TeX or another format?", "kind": "definition", "id": "latex-format-and-root-evidence-q01" }, { "text": "Which file is the entry point for each intended document, and which files are included fragments?", "kind": "boundary", "id": "latex-format-and-root-evidence-q02" } ] } ] }, { "id": "source-authority", "name": "Source authority", "description": "Distinguish editable source from generated content and externally maintained templates.", "findings": [ { "id": "authored-and-derived-files", "name": "Authored and derived files", "description": "Identify where durable edits belong and where changes would be overwritten or break template expectations.", "questions": [ { "text": "Which .tex, .cls and .sty files are authored here, supplied externally or generated from another source?", "kind": "provenance", "id": "authored-and-derived-files-q01" }, { "text": "Should the requested change be made in LaTeX source, an upstream generator or an allowed template customisation point?", "kind": "action", "id": "authored-and-derived-files-q02" } ] } ] } ] }, { "id": "document-semantics-and-macros", "name": "Document semantics and macros", "description": "Capture how LaTeX markup expresses the document's structure and recurring notation.", "rationale": "Visually similar output can arise from structurally different markup, with different consequences for editing, numbering and reuse.", "layers": [ { "id": "structural-markup", "name": "Structural markup", "description": "Assess the use of sectioning, environments, counters and labels.", "findings": [ { "id": "structure-and-reference-integrity", "name": "Structure and reference integrity", "description": "Record how logical document elements are declared, numbered and referenced.", "questions": [ { "text": "Which commands and environments represent sections, figures, tables, equations and theorem-like statements?", "kind": "definition", "id": "structure-and-reference-integrity-q01" }, { "text": "Which labels are duplicated or unresolved, and where does manually written numbering bypass LaTeX counters or references?", "kind": "measurement", "id": "structure-and-reference-integrity-q02" } ] } ] }, { "id": "notation-and-command-interfaces", "name": "Notation and command interfaces", "description": "Understand custom macros and mathematical markup before changing their definitions or uses.", "findings": [ { "id": "macro-contracts-and-math-intent", "name": "Macro contracts and mathematical intent", "description": "Record the arguments, expected contexts and document-wide effects of recurring commands.", "questions": [ { "text": "Which custom commands encode recurring concepts or notation, and what arguments and text or math contexts do they require?", "kind": "definition", "id": "macro-contracts-and-math-intent-q01" }, { "text": "Would changing a macro definition preserve its existing uses, spacing, numbering and behaviour in headings or captions?", "kind": "action", "id": "macro-contracts-and-math-intent-q02" } ] } ] } ] }, { "id": "class-package-and-engine-contract", "name": "Class, package and engine contract", "description": "Establish the LaTeX components and compatibility constraints that govern compilation and presentation.", "rationale": "A document's behaviour depends on the selected class, package interactions and engine capabilities, not source text alone.", "layers": [ { "id": "class-and-package-composition", "name": "Class and package composition", "description": "Identify the loaded extensions and the interfaces they expose or override.", "findings": [ { "id": "extension-compatibility", "name": "Extension compatibility", "description": "Record class options, package options, loading order and relevant command redefinitions.", "questions": [ { "text": "Which class and packages are loaded, including local copies, and what options or loading-order requirements are evidenced?", "kind": "provenance", "id": "extension-compatibility-q01" }, { "text": "Which observed errors or behaviour changes arise from option clashes, redefined commands or incompatible extensions?", "kind": "measurement", "id": "extension-compatibility-q02" } ] } ] }, { "id": "engine-font-and-language-support", "name": "Engine, font and language support", "description": "Determine which compilation environment can support the document's typography and scripts.", "findings": [ { "id": "engine-and-text-requirements", "name": "Engine and text requirements", "description": "Record engine assumptions and the availability of required fonts, encodings and language support.", "questions": [ { "text": "What source declarations or build instructions establish the required engine, fonts and language configuration?", "kind": "provenance", "id": "engine-and-text-requirements-q01" }, { "text": "Are required glyphs, hyphenation patterns and writing directions supported in the tested environment?", "kind": "measurement", "id": "engine-and-text-requirements-q02" } ] } ] } ] }, { "id": "compilation-and-derived-state", "name": "Compilation and derived state", "description": "Represent the build sequence, its execution requirements and the validity of generated results.", "rationale": "LaTeX output may depend on repeated passes, auxiliary files and external processors whose state affects correctness.", "layers": [ { "id": "build-recipe-and-execution", "name": "Build recipe and execution", "description": "Identify the commands, inputs and permissions required to produce the intended output.", "findings": [ { "id": "complete-build-workflow", "name": "Complete build workflow", "description": "Record the compilation recipe, including bibliography, indexing and externally generated material.", "questions": [ { "text": "Which engine invocations and bibliography, index, glossary or graphics-processing steps are required, and in what dependency order?", "kind": "definition", "id": "complete-build-workflow-q01" }, { "text": "Does any step require shell escape, external executables or file access beyond the permitted build environment?", "kind": "boundary", "id": "complete-build-workflow-q02" } ] } ] }, { "id": "convergence-and-reproducibility", "name": "Convergence and reproducibility", "description": "Distinguish a completed invocation from a stable, traceable document build.", "findings": [ { "id": "validated-build-state", "name": "Validated build state", "description": "Associate output and diagnostics with the source state and environment that produced them.", "questions": [ { "text": "After the prescribed build sequence, which errors, undefined citations, unresolved references or rerun requests remain?", "kind": "measurement", "id": "validated-build-state-q01" }, { "text": "Can a clean build from the recorded inputs and tool versions reproduce the intended output to the project's required level of equivalence?", "kind": "measurement", "id": "validated-build-state-q02" } ] } ] } ] }, { "id": "typeset-output-and-handoff", "name": "Typeset output and handoff", "description": "Assess the rendered document and determine whether its source and output are ready for their intended use.", "rationale": "Compilation success does not establish acceptable pagination, readable mathematics, accessible structure or a usable submission package.", "layers": [ { "id": "rendered-document-quality", "name": "Rendered document quality", "description": "Connect build diagnostics to visual inspection and stated output requirements.", "findings": [ { "id": "layout-and-reading-quality", "name": "Layout and reading quality", "description": "Record visible defects and the evidence used to assess typography and document navigation.", "questions": [ { "text": "Where do rendered pages show clipped material, poor line breaks, misplaced floats, unreadable equations or missing glyphs?", "kind": "measurement", "id": "layout-and-reading-quality-q01" }, { "text": "Which requirements apply to links, bookmarks, reading order, tagging or mathematical accessibility, and which have been verified on the actual output?", "kind": "boundary", "id": "layout-and-reading-quality-q02" } ] } ] }, { "id": "submission-and-source-handoff", "name": "Submission and source handoff", "description": "Determine whether the deliverable matches recipient constraints and includes sufficient build material.", "findings": [ { "id": "deliverable-readiness", "name": "Deliverable readiness", "description": "Record the required submission form and identify missing or unsuitable handoff components.", "questions": [ { "text": "What class, engine, bibliography, asset and output constraints does the intended recipient impose?", "kind": "boundary", "id": "deliverable-readiness-q01" }, { "text": "Which authored sources, local extensions, assets, generated bibliography files and build instructions must be included for this handoff?", "kind": "action", "id": "deliverable-readiness-q02" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-kinds", "name": "Kinds and varieties", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "LaTeX 2.09 (historical format, superseded)", "LaTeX2e (current stable kernel, 1994-present)", "LaTeX3 / expl3 (programming layer and ongoing kernel rewrite)", "Plain TeX (related but not LaTeX)", "ConTeXt (related TeX format, not LaTeX)", "XeLaTeX (Unicode/OpenType engine path)", "LuaLaTeX (LuaTeX engine path)", "pdfLaTeX (pdfTeX engine path)" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of LaTeX this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "scheme": "Wikidata", "value_or_pattern": "Q5310", "note": "Primary item for the LaTeX document preparation system." }, { "scheme": "CTAN package", "value_or_pattern": "latex", "note": "Canonical TeX archive package name for the LaTeX kernel." }, { "scheme": "Library of Congress Name Authority", "value_or_pattern": "n92061002", "note": "LCNAF identifier recorded on Wikidata for LaTeX." }, { "scheme": "GND", "value_or_pattern": "4259186-1", "note": "German National Library subject heading for LaTeX." }, { "scheme": "MIME type", "value_or_pattern": "application/x-latex", "note": "Common unofficial media type for .tex/.ltx source; not an IANA-registered type for LaTeX itself." }, { "scheme": "File extension", "value_or_pattern": ".tex | .ltx | .sty | .cls | .dtx", "note": "Source, class/style, and documented-source file patterns used in LaTeX workflows." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of LaTeX this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "LaTeX2e kernel and documented interfaces - issued by the LaTeX Project / LaTeX3 team (not an ISO/IEC language standard).", "TeX engine behaviour (the substrate LaTeX macros run on) - Donald Knuth's TeX, with engine variants pdfTeX, XeTeX, LuaTeX maintained in the TeX community.", "ISO 32000 (PDF) - International Organization for Standardization; governs the PDF files that pdfLaTeX, XeLaTeX, and LuaLaTeX typically produce.", "ISO 32000-2:2020 (PDF 2.0) - ISO; current PDF language standard relevant to tagged/accessible PDF output from LaTeX.", "EPUB / W3C publishing notes - relevant when LaTeX is converted to HTML/EPUB; they govern the conversion target, not LaTeX source.", "No statute exclusively regulates LaTeX as a document language; journal and thesis class files act as de facto house standards." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of LaTeX this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Authoring mathematics-heavy journal articles, preprints, and books, often submitted as .tex plus a journal class (e.g. elsarticle, IEEEtran, amsart).", "University theses and dissertations compiled with faculty or graduate-school .cls files.", "Conference proceedings and arXiv/institutional-repository deposits, commonly compiled with pdfLaTeX, XeLaTeX, or LuaLaTeX.", "Technical documentation, lecture notes, problem sheets, and beamer slide decks.", "Automated report generation from scientific pipelines (Rnw/knitr, Python+pylatex, pandoc targeting LaTeX).", "Publisher production: copy-editing and typesetting of STM content from author LaTeX through to PDF or XML.", "Overleaf and similar cloud editors as the common collaborative authoring surface." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of LaTeX this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "quantity": "Paper size", "typical_range": "A4 (210×297) or US letter (8.5×11)", "unit": "mm or in" }, { "quantity": "Type size (document class option)", "typical_range": "10, 11, or 12", "unit": "pt" }, { "quantity": "Text width / typeblock", "typical_range": "about 120-160 on A4 article defaults", "unit": "mm" }, { "quantity": "Baseline skip / leading", "typical_range": "about 12-15 for 10-12 pt body", "unit": "pt" }, { "quantity": "Engine TeX capacity (main memory, hash size)", "typical_range": "engine- and distro-dependent; large documents may exhaust defaults", "unit": "words (TeX memory units)" }, { "quantity": "Compile time", "typical_range": "seconds for a paper; minutes for a book with indexes, bibliographies, and multiple passes", "unit": "s" }, { "quantity": "Output PDF version", "typical_range": "1.4-1.7 commonly; 2.0 when explicitly requested", "unit": "PDF version number" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of LaTeX this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Undefined control sequence, missing package, or class/package version skew that stops compilation.", "Overfull/underfull hboxes and unbreakable math that produce poor line breaks or overflow into margins.", "Bibliography/citation failures (BibTeX vs biblatex/biber mismatch, unresolved keys).", "Engine mismatch: a document written for XeLaTeX/LuaLaTeX (fontspec, Unicode) failing under pdfLaTeX.", "Fragile commands in moving arguments (TOC, captions) causing expansion errors.", "Non-reproducible builds: implicit font, encoding, or package-version dependence across TeX Live/MiKTeX years.", "Unstable auxiliary files (.aux, .toc, .bbl) after a failed run, requiring a clean rebuild.", "Accessibility and archival risk: visual PDF without tagged structure, or source that cannot be recompiled later.", "Security: \\write18 / --shell-escape enabling arbitrary command execution from a malicious .tex file.", "License/distribution confusion when mixing LPPL packages with non-free fonts or publisher classes." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of LaTeX this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Paper and layout defaults: A4 and millimetre-based classes dominate outside the US; US letter and inch-based templates are common in North America.", "Language and hyphenation: babel vs polyglossia, and engine choice (pdfLaTeX vs Xe/LuaLaTeX) vary with script; CJK, Arabic, and Indic work typically requires XeLaTeX or LuaLaTeX plus language packages.", "Typography conventions: quotation marks, decimal commas vs points, and theorem-numbering styles differ by language community and publisher.", "Distribution: TeX Live is the default on most Unix-like systems and Overleaf; MiKTeX remains widely used on Windows.", "Naming: spoken as \"Lay-tech\" or \"Lah-tech\"; written LaTeX, LATEX, or latex; in some locales the TeX logo is not reproduced and \"LaTeX\" is used as plain text.", "Publisher practice: many European STM houses still require or strongly prefer LaTeX; some US humanities and legal venues do not." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of LaTeX this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "name": "TeX", "difference": "TeX is Knuth's typesetting engine and primitive language; LaTeX is a macro format on top of TeX. A file that begins with \\documentclass is LaTeX; one that uses \\shipout / plain primitives without a LaTeX kernel is TeX." }, { "name": "Plain TeX", "difference": "Plain TeX is Knuth's minimal format. Presence of \\documentclass / \\begin{document} vs plain macros (\\proclaim, \\eqalign) separates them; they are not interchangeable formats." }, { "name": "ConTeXt", "difference": "Another TeX format with its own kernel (\\starttext / \\setup…), not the LaTeX class/package model. Engine overlap (LuaTeX) does not make a ConTeXt document a LaTeX document." }, { "name": "XeTeX / LuaTeX / pdfTeX", "difference": "These are engines, not formats. XeLaTeX means the LaTeX format running on XeTeX. Engine can change while the source remains LaTeX; format is decided by the kernel (latex vs plain vs context)." }, { "name": "Markdown / pandoc", "difference": "Lightweight markup often compiled *to* LaTeX. If the source of truth is .md plus a YAML header, it is Markdown; if it is a .tex file with a document class, it is LaTeX." }, { "name": "Typst / Word / InDesign", "difference": "Independent typesetting or DTP systems. They may import or export LaTeX-like math, but they do not execute the LaTeX kernel; round-trip is lossy." }, { "name": "MathJax / KaTeX", "difference": "JavaScript engines that parse a subset of LaTeX math notation for the web; they do not process a full LaTeX document (no classes, floats, or aux-file workflow)." }, { "name": "LaTeX the typesetting system vs latex the rubber polymer", "difference": "Homograph only. In computing and publishing contexts, capitalisation (LaTeX) and file/engine artefacts (.tex, pdfLaTeX) identify the document system; the polymer is a material with CAS/ISO rubber identifiers." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of LaTeX this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend LaTeX to denote the document preparation system alone, or also individual LaTeX source projects as model instances?", "Does an existing Vercy world model already own this concept or any of its document-build responsibilities?", "Which current authoritative LaTeX, engine and package documentation should support the compatibility and build-state criteria?", "Which accessibility targets and validation methods should determine readiness for the intended document uses?", "Should reproducibility mean equivalent content, equivalent layout or byte-identical output for this registry entry?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 28 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "work, medium or creative form", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a LaTeX, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a LaTeX document system, assess whether its sources can produce the intended document reliably, and decide which editing, compilation and distribution actions are appropriate.", "characteristics": { "substance": "information", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "read and interpreted", "observed and measured" ], "distinguishingFeatures": [ "Described in 95 Wikipedia languages, which is a measure of how widely the thing is known, not of how important it is." ], "openQuestionsForResearch": [ "Which of the bundles below does a real task actually need, and which are ceremony?", "What does this thing have that the facets do not capture at all?", "Which neighbouring kind is most often confused with a LaTeX, and on what evidence are they told apart?" ], "whatItIsMadeOf": "content that has to be carried by something else", "physicalCharacter": [ "Does nothing on its own; everything it does, something else did to it.", "These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing." ], "whatCanBeDoneWithIt": [ "read it and act on what it says", "observe it, measure it, record its state" ], "howItIsRecognised": [ "What is seen is a copy or a performance, not the work. Recognising the work means recognising the content through whatever is carrying it." ], "relatedModels": [], "standing": "Described in 95 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one LaTeX from another, and a LaTeX from things that resemble it.", "rationale": "Recognition comes before every other claim. Without stable identity nothing else in the model can be trusted to be about the same thing twice.", "layers": [ { "id": "naming-and-identifiers", "name": "Names and identifiers", "description": "The names this thing goes by and the identifiers that survive translation and time.", "findings": [ { "id": "preferred-name-and-aliases", "name": "Preferred name, aliases and local names", "description": "Which name to use, which names mean the same thing, and which merely sound similar.", "questions": [ { "id": "preferred-name-and-aliases-q01", "text": "What identifies and describes the name of a LaTeX, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "preferred-name-and-aliases-q02", "text": "Who or what asserted this about the name of a LaTeX, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "preferred-name-and-aliases-q03", "text": "What may an agent decide or do once the name of a LaTeX is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "stable-identifiers", "name": "Stable identifiers and external keys", "description": "Identifiers that keep pointing at this kind of thing across systems and languages.", "questions": [ { "id": "stable-identifiers-q01", "text": "What identifies and describes an identifier for a LaTeX, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stable-identifiers-q02", "text": "Who or what asserted this about an identifier for a LaTeX, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stable-identifiers-q03", "text": "What may an agent decide or do once an identifier for a LaTeX is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "classification-and-granularity", "name": "Classification and granularity", "description": "Where a LaTeX sits among kinds, and how finely a task needs to cut it.", "findings": [ { "id": "kind-and-parents", "name": "Kind, parents and neighbouring kinds", "description": "The classes this thing belongs to and the ones it is next to.", "questions": [ { "id": "kind-and-parents-q01", "text": "What identifies and describes the kind of a LaTeX, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "kind-and-parents-q02", "text": "Who or what asserted this about the kind of a LaTeX, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "kind-and-parents-q03", "text": "What may an agent decide or do once the kind of a LaTeX is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "distinguishing-features", "name": "Distinguishing features", "description": "What separates a LaTeX from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a LaTeX, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "distinguishing-features-q02", "text": "Who or what asserted this about what distinguishes a LaTeX, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "distinguishing-features-q03", "text": "What may an agent decide or do once what distinguishes a LaTeX is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "state-and-lifecycle", "name": "State and lifecycle", "description": "The states a LaTeX passes through and the events that move it between them.", "rationale": "Most decisions about a thing depend on what state it is in now, which is a claim with a time on it, not a property.", "layers": [ { "id": "lifecycle-stages", "name": "Lifecycle stages", "description": "From coming into existence to ceasing to be one of these.", "findings": [ { "id": "stages-and-transitions", "name": "Stages and transitions", "description": "The stages worth naming and what moves a LaTeX between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a LaTeX, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stages-and-transitions-q02", "text": "Who or what asserted this about the lifecycle of a LaTeX, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stages-and-transitions-q03", "text": "What may an agent decide or do once the lifecycle of a LaTeX is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "observations-and-status", "name": "Observations and current status", "description": "What is observed about a LaTeX, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a LaTeX is recorded so that it can be superseded rather than overwritten.", "questions": [ { "id": "observation-record-q01", "text": "What identifies and describes an observation of a LaTeX, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "observation-record-q02", "text": "Who or what asserted this about an observation of a LaTeX, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "observation-record-q03", "text": "What may an agent decide or do once an observation of a LaTeX is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "content-and-access", "name": "Content, encoding and access", "description": "What a LaTeX says, how it is encoded and who may read it.", "rationale": "An informational thing carries content that can be copied, versioned and withheld, none of which its physical carrier explains.", "layers": [ { "id": "content-and-encoding", "name": "Content and encoding", "description": "The content itself, its format and its language.", "findings": [ { "id": "content-and-format", "name": "Content, format and language", "description": "What a LaTeX contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a LaTeX, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "content-and-format-q02", "text": "Who or what asserted this about the content of a LaTeX, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "content-and-format-q03", "text": "What may an agent decide or do once the content of a LaTeX is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "access-and-rights", "name": "Access, rights and retention", "description": "Who may read, copy or change it, and for how long it is kept.", "findings": [ { "id": "access-rules", "name": "Access rules and retention", "description": "The permissions attached to a LaTeX and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a LaTeX, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "access-rules-q02", "text": "Who or what asserted this about access to a LaTeX, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "access-rules-q03", "text": "What may an agent decide or do once access to a LaTeX is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "work-and-manifestation", "name": "Work, version and copy", "description": "Which level of LaTeX a statement is about.", "rationale": "The work, the edition, the file and the copy in hand are four things; rights and content attach to different ones.", "layers": [ { "id": "levels", "name": "Levels of the thing", "description": "Work, expression, manifestation and item, in plain terms.", "findings": [ { "id": "level-rules", "name": "What belongs at each level", "description": "Which facts hold for the work and which only for one copy.", "questions": [ { "id": "level-rules-q01", "text": "For LaTeX, which facts belong to the work itself, which to a version, and which to a single copy?", "kind": "boundary" }, { "id": "level-rules-q02", "text": "What identifier exists at each level, and which one is being cited?", "kind": "definition" } ] } ] }, { "id": "versions", "name": "Versions, editions and variants", "description": "How versions differ and which is canonical to whom.", "findings": [ { "id": "version-record", "name": "Versions and canonicity", "description": "Differences that matter and who calls one authoritative.", "questions": [ { "id": "version-record-q01", "text": "Which versions or editions of LaTeX exist, and how do they differ substantively?", "kind": "definition" }, { "id": "version-record-q02", "text": "Who treats which version as authoritative, and for what purpose?", "kind": "provenance" } ] } ] } ] }, { "id": "authorship-and-rights", "name": "Authorship, rights and permitted use", "description": "Who made LaTeX and what may be done with it.", "rationale": "Rights are jurisdictional, time-limited and attached to a level, and an agent that ignores that will copy what it may not.", "layers": [ { "id": "authorship", "name": "Authorship and contribution", "description": "Who contributed what, and in what capacity.", "findings": [ { "id": "contribution-record", "name": "Contributors and roles", "description": "The people and bodies behind it, with their roles.", "questions": [ { "id": "contribution-record-q01", "text": "Who authored or contributed to LaTeX, in what roles, and how is that attested?", "kind": "provenance" }, { "id": "contribution-record-q02", "text": "Where authorship is disputed or anonymous, what is recorded instead?", "kind": "boundary" } ] } ] }, { "id": "rights", "name": "Rights and permissions", "description": "Which rights subsist, where, until when, and what they permit.", "findings": [ { "id": "rights-record", "name": "Rights, term and permitted acts", "description": "The regime in force and what it allows.", "questions": [ { "id": "rights-record-q01", "text": "What rights subsist in LaTeX, in which jurisdictions, and until when?", "kind": "definition" }, { "id": "rights-record-q02", "text": "Which acts are permitted without further permission, and which must an agent refuse?", "kind": "action" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a LaTeX came from and when it held.", "rationale": "A claim without a source and a time cannot be superseded, only overwritten, and an agent that overwrites loses the ability to explain itself.", "layers": [ { "id": "source-and-authority", "name": "Source and authority", "description": "Who said it, on what evidence, and how strongly.", "findings": [ { "id": "claim-provenance", "name": "Claim provenance and confidence", "description": "The authority behind each claim about a LaTeX and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a LaTeX, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "claim-provenance-q02", "text": "Who or what asserted this about a claim about a LaTeX, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "claim-provenance-q03", "text": "What may an agent decide or do once a claim about a LaTeX is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "time-and-versions", "name": "Time, versions and supersession", "description": "When a claim was true, when it was learnt, and what replaced it.", "findings": [ { "id": "validity-and-supersession", "name": "Validity period and supersession", "description": "How an old claim about a LaTeX is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a LaTeX, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "validity-and-supersession-q02", "text": "Who or what asserted this about the validity of a claim about a LaTeX, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "validity-and-supersession-q03", "text": "What may an agent decide or do once the validity of a claim about a LaTeX is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 6, "layers": 12, "findings": 14, "questions": 38 } } } }