{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.tr.latex","code":"thing-q5310","url":"https://ver.cy/models/thing/q5310/","name":"LaTeX","alternateNames":[],"kind":"thing","status":"published","version":"0.1.0-research.1","language":"en","classifiers":{"family":"Thing Registry","category":"Information and virtual systems","entryKind":"thing","plane":"INF","domain":["INF.MED"],"industry":[],"navPath":"","tags":[],"facets":{}},"whatItIs":"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.","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.","scope":{"in":["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":["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"],"boundaries":[]},"distinguishingFeatures":["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."],"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.","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?","id":"latex-format-and-root-evidence-q01","kind":"definition"},{"text":"Which file is the entry point for each intended document, and which files are included fragments?","id":"latex-format-and-root-evidence-q02","kind":"boundary"}]}]},{"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?","id":"authored-and-derived-files-q01","kind":"provenance"},{"text":"Should the requested change be made in LaTeX source, an upstream generator or an allowed template customisation point?","id":"authored-and-derived-files-q02","kind":"action"}]}]}]},{"id":"document-semantics-and-macros","name":"Document semantics and macros","description":"Capture how LaTeX markup expresses the document's structure and recurring notation.","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?","id":"structure-and-reference-integrity-q01","kind":"definition"},{"text":"Which labels are duplicated or unresolved, and where does manually written numbering bypass LaTeX counters or references?","id":"structure-and-reference-integrity-q02","kind":"measurement"}]}]},{"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?","id":"macro-contracts-and-math-intent-q01","kind":"definition"},{"text":"Would changing a macro definition preserve its existing uses, spacing, numbering and behaviour in headings or captions?","id":"macro-contracts-and-math-intent-q02","kind":"action"}]}]}]},{"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.","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?","id":"extension-compatibility-q01","kind":"provenance"},{"text":"Which observed errors or behaviour changes arise from option clashes, redefined commands or incompatible extensions?","id":"extension-compatibility-q02","kind":"measurement"}]}]},{"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?","id":"engine-and-text-requirements-q01","kind":"provenance"},{"text":"Are required glyphs, hyphenation patterns and writing directions supported in the tested environment?","id":"engine-and-text-requirements-q02","kind":"measurement"}]}]}]},{"id":"compilation-and-derived-state","name":"Compilation and derived state","description":"Represent the build sequence, its execution requirements and the validity of generated results.","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?","id":"complete-build-workflow-q01","kind":"definition"},{"text":"Does any step require shell escape, external executables or file access beyond the permitted build environment?","id":"complete-build-workflow-q02","kind":"boundary"}]}]},{"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?","id":"validated-build-state-q01","kind":"measurement"},{"text":"Can a clean build from the recorded inputs and tool versions reproduce the intended output to the project's required level of equivalence?","id":"validated-build-state-q02","kind":"measurement"}]}]}]},{"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.","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?","id":"layout-and-reading-quality-q01","kind":"measurement"},{"text":"Which requirements apply to links, bookmarks, reading order, tagging or mathematical accessibility, and which have been verified on the actual output?","id":"layout-and-reading-quality-q02","kind":"boundary"}]}]},{"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?","id":"deliverable-readiness-q01","kind":"boundary"},{"text":"Which authored sources, local extensions, assets, generated bibliography files and build instructions must be included for this handoff?","id":"deliverable-readiness-q02","kind":"action"}]}]}]},{"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.","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.","questions":[{"text":"Which of these kinds and varieties hold for the sense of LaTeX this model covers, and on what evidence?","id":"evidence-kinds-q01","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.","questions":[{"text":"Which of these identifiers and schemes hold for the sense of LaTeX this model covers, and on what evidence?","id":"evidence-identifiers-q01","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.","questions":[{"text":"Which of these standards and regulation hold for the sense of LaTeX this model covers, and on what evidence?","id":"evidence-standards-and-regulation-q01","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.","questions":[{"text":"Which of these real-world use hold for the sense of LaTeX this model covers, and on what evidence?","id":"evidence-real-world-use-q01","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.","questions":[{"text":"Which of these typical measurements hold for the sense of LaTeX this model covers, and on what evidence?","id":"evidence-measurements-q01","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.","questions":[{"text":"Which of these failure modes and hazards hold for the sense of LaTeX this model covers, and on what evidence?","id":"evidence-failure-modes-and-hazards-q01","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.","questions":[{"text":"Which of these regional variation hold for the sense of LaTeX this model covers, and on what evidence?","id":"evidence-regional-variation-q01","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.","questions":[{"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?","id":"evidence-neighbours-q01","kind":"provenance"}]}]}]}]},"agentConduct":{"may":["Write, edit and compile documents for a user.","Explain commands and fix errors in a user's source."],"mustNot":["Run untrusted documents with shell escape enabled.","Use it to fabricate documents that imitate official papers, journals or certificates.","Remove authors, acknowledgements or licence notices from templates and packages.","Write a student's assessed work where help is not allowed."],"requiresHuman":["Submitting a manuscript or document on someone's behalf."]},"ethics":{"considerations":["Polished typesetting can make fabricated research look credible.","Package authors rely on attribution and licence terms."],"affectedParties":["Authors and readers","Package maintainers","Students"]},"owners":{"steward":"Nobody owns the documents it produces; the community project maintains the system.","roles":[],"masterSystems":[]},"relations":[{"target":"Q37045","type":"parent","note":"registry parent class"}],"interaction":{"identity":{"applicability":"required","items":["Vercy registry: vr.tr.latex","Wikidata: Q5310 (https://www.wikidata.org/wiki/Q5310)"]},"properties":{"applicability":"not-applicable","items":["Source role: document entry point | included fragment | class | package | generated source","Document class: class name, options, origin and required version when known","Required compilation engine: pdfTeX | XeTeX | LuaTeX | other specified engine | unresolved","Dependency resolution: resolved | missing | conflicting | unverified","Build convergence: not attempted | failed | rerun required | converged under recorded checks","Unresolved references and citations: count from the latest identified build","Typesetting diagnostics: counts of overfull and underfull boxes, with locations and review status","External execution requirement: none identified | restricted execution required | unrestricted execution required | unknown","Output freshness: matches recorded inputs | stale | provenance unknown"]},"recognition":{"applicability":"optional","items":["Plain text source files ending in .tex, full of commands that start with a backslash.","Output with characteristic typeset mathematics and serif fonts."]},"capabilities":{"applicability":"required","items":["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."]},"hazards":{"applicability":"required","items":["Shell escape can let a malicious document run commands on the computer.","Compiling untrusted packages can read or write local files."]},"interfaces":{"applicability":"not-applicable","items":[]},"context":{"applicability":"required","items":["This document markup language is used to prepare scientific papers, technical reports, books and other publications with structured content.","Authors express headings, equations, citations and cross-references in source files that a compatible typesetting system compiles into formatted documents.","It is especially useful when complex mathematics and consistent formatting must be maintained across repeated revisions."]}},"sources":[{"title":"LaTeX - A document preparation system","url":"https://www.latex-project.org/","note":"Official project definition of LaTeX as a TeX macro package, current LaTeX2e kernel, and LaTeX3/expl3 work."},{"title":"latex - A TeX macro package that defines LaTeX","url":"https://ctan.org/pkg/latex","note":"Canonical package identity on CTAN, LaTeX2e as current version, historical 2.09, and relationship to TeX."},{"title":"LaTeX (Q5310)","url":"https://www.wikidata.org/wiki/Q5310","note":"Stable identifiers (Wikidata Q5310, Freebase, Library of Congress, GND) and classification as a document markup language / typesetting system."},{"title":"ISO 32000-2:2020 Document management - Portable document format - Part 2: PDF 2.0","url":"https://www.iso.org/standard/75839.html","note":"The principal interchange standard for the PDF files LaTeX engines commonly emit; not a LaTeX specification itself."},{"title":"Wikipedia: LaTeX","url":"https://en.wikipedia.org/wiki/LaTeX","note":"general description of the item"}],"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?"],"resources":{"spec":"/models/things/publications/thing-q5310/spec.json"},"provenance":{"origin":"thing registry research (pass 2)","builtFrom":["models/things/publications/thing-q5310/spec.json"],"providers":["Codex","Grok"],"researchStatus":"unreviewed","generatedAt":"2026-09-07T13:25:11Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"not-applicable","interaction.context":"filled","sources":"filled"},"notes":{"_gate":"Published through the thing publication gate 1.0 on 2026-10-07T10:10:31+00:00: completeness 1.00; sense: Wikidata description; 4 live sources; review by codex: pass","interaction.properties":"Plane INF: no invented physical properties.","interaction.interfaces":"The markup language itself has no universally applicable formal standard or regulation, while requirements for generated documents depend on their output format and intended use."},"score":1.0}}