{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T10:17:24Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 14.5, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\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: 01a0951e-014b-70d0-88ae-3951427c65cd\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Hoefler Text\nSense to describe: (none recorded)\nDomain code: ACT.ACT\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 043: 1001 re", "usd": 0.0, "recall": true }, "codex": { "seconds": 78.3, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\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: 01a0951e-013e-7d91-8fda-47d12be29c45\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Hoefler Text\nRegistry id: vr.tr.hoefler-text\nPlane / domain: ACT / ACT.ACT\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:45:15+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "standards_and_regulation", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:26+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q1622796", "registryId": "vr.tr.hoefler-text", "name": "Hoefler Text", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "ACT.ACT" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q1622796/", "model": { "registry_id": "vr.tr.hoefler-text", "name": "Hoefler Text", "purpose": "Enable an agent to identify Hoefler Text, assess a particular font implementation, and choose supported, authorized ways to typeset with it.", "definition": "Hoefler Text is a serif typeface family designed by Jonathan Hoefler and released in 1991, drawing on historical book typography and incorporating features for sophisticated text composition.", "scope_statement": "This model owns the Hoefler Text typeface family registered as vr.tr.hoefler-text, its identifying design, family membership, implementation differences, and conditions of use; individual font files are evidence-bearing implementations of that family.", "in_scope": [ "Hoefler Text family identity and documented attribution", "Relationships among text faces, italic faces, weight variants, and associated ornaments", "Version-specific character coverage and typographic features", "Rendering, text composition, and substitution behavior", "Distribution provenance and evidence governing intended uses" ], "out_of_scope": [ "Jonathan Hoefler's biography and other typeface designs", "Hoefler&Co. as a business or its complete catalogue", "Hoefler Titling as a separately modeled typeface family", "General histories and classifications of serif typography", "Document content, editorial policy, and complete page-layout systems", "Operating-system font management beyond its effect on Hoefler Text" ], "distinguishing_features": [ "Require family-name metadata corroborated by an authoritative specimen or distribution record; a visually similar serif face is insufficient identification.", "Distinguish the named family Hoefler Text from its creator, its supplier, and neighboring Hoefler Titling; the supplier lists Text and Titling separately. See [Hoefler Text catalogue](https://www.typography.com/fonts/hoefler-text/overview).", "For an Apple implementation, compare face identifiers against documented examples such as HoeflerText-Regular, HoeflerText-Italic, HoeflerText-Black, and HoeflerText-BlackItalic. See [Apple font documentation](https://developer.apple.com/documentation/applenews/applying-apple-news-format-fonts).", "Treat HoeflerText-Ornaments as a distinct ornamental resource when encountered, rather than interpreting its glyphs as ordinary running-text letters. See [Apple font documentation](https://developer.apple.com/documentation/applenews/applying-apple-news-format-fonts).", "Use file version, source, and demonstrated feature behavior to distinguish implementations sharing the Hoefler Text name; family identity alone does not establish interchangeability." ], "characteristics": [ { "name": "Family identity evidence", "kind": "relation", "unit_or_values": "Font naming records linked to supplier specimens or documented distributions", "why_it_matters": "Separates confirmed Hoefler Text implementations from aliases, substitutions, and visual guesses." }, { "name": "Face role", "kind": "category", "unit_or_values": "Upright text, italic text, documented weight variant, ornaments; retain exact supplied names", "why_it_matters": "Prevents selecting ornaments for prose or substituting synthetic styling for a supplied face." }, { "name": "Implementation provenance", "kind": "relation", "unit_or_values": "Distributor, package, filename, internal version, and file fingerprint", "why_it_matters": "Makes comparisons and reproduction specific to the font actually used." }, { "name": "Required-text coverage", "kind": "measurement", "unit_or_values": "Percentage of required characters and tested sequences rendered without fallback", "why_it_matters": "Determines whether this implementation can compose the intended text." }, { "name": "Typographic feature availability", "kind": "state", "unit_or_values": "For each requested feature: absent, present but inaccessible, selectable, or verified in output", "why_it_matters": "Separates font capability from what the target application can activate." }, { "name": "Composition behavior", "kind": "measurement", "unit_or_values": "Line count, line-ending differences, and clipping count for a fixed specimen and layout", "why_it_matters": "Detects changes caused by implementation replacement, fallback, or export." }, { "name": "Intended-use authorization", "kind": "state", "unit_or_values": "Verified permitted, verified restricted, or unresolved for the proposed action and acquired package", "why_it_matters": "Provides an evidence-based gate for embedding, serving, or redistributing font software." } ], "affordances": [ "Identify an installed Hoefler Text face and record its implementation provenance.", "Select verified text faces and weights for a document's typographic hierarchy.", "Test requested ligatures, small capitals, numeral forms, and alternates where the implementation supplies them.", "Inspect and place associated ornaments using verified glyph mappings.", "Compare composition before and after replacing a Hoefler Text implementation or exporting a document.", "Determine whether a proposed embedding or deployment action is supported by the acquired package and its terms." ], "agent_conduct": { "may": [ "Identify the typeface in documents or images and describe its features.", "Advise on the licence terms that govern its use." ], "must_not": [ "Distribute font files in breach of their licence.", "Present a lookalike font as the original.", "Misattribute the design." ], "requires_human": [ "Licensing decisions for an organization." ] }, "ethics": { "considerations": [ "Type designers' work is protected and deserves fair payment.", "Typefaces shape readability and accessibility of texts." ], "affected_parties": [ "Type designers", "Readers", "Licensees" ] }, "owners": { "steward": "The rights holder for the font software.", "master_systems": [] }, "visual_identification": [ "A classical serif text face with old-style figures and refined, slightly calligraphic details.", "Comes with italics, small caps and ornaments." ], "failure_modes_and_hazards": [ "Unlicensed use leads to legal claims.", "Substitution changes layout and readability." ], "standards_and_regulation": [ "ISO/IEC 14496-22 Open Font Format, International Organization for Standardization and International Electrotechnical Commission." ], "what_it_is_for": [ "This serif typeface family is used in books, essays and other documents requiring sustained reading and historically influenced typography.", "It supports text composition where a particular font implementation provides features such as ligatures, small capitals and alternate numeral forms.", "Use in print or digital documents depends on available glyphs, layout support and the permissions attached to the font files." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q1622796: Hoefler Text", "url": "https://www.wikidata.org/wiki/Q1622796", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Hoefler Text", "url": "https://en.wikipedia.org/wiki/Hoefler_Text", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "family-identity-and-boundaries", "name": "Family identity and boundaries", "description": "Recognize Hoefler Text as a named typeface family and keep adjacent identities distinct.", "rationale": "The registry supplies only a name, so recognition must establish the referent before evaluating its fonts.", "layers": [ { "id": "identity-evidence", "name": "Identity evidence", "description": "Connect the registered name to documentary and visual evidence.", "findings": [ { "id": "corroborated-family-identification", "name": "Corroborated family identification", "description": "Identify the candidate through naming records and a matching documented specimen, recording uncertainty when only appearance is available.", "questions": [ { "text": "Which internal family and face names identify the candidate as Hoefler Text?", "kind": "definition", "id": "corroborated-family-identification-q01" }, { "text": "Which authoritative specimen or distribution record corroborates that identification?", "kind": "provenance", "id": "corroborated-family-identification-q02" } ] } ] }, { "id": "neighboring-designs", "name": "Neighboring designs", "description": "Separate family membership from authorship, supplier identity, and related designs.", "findings": [ { "id": "text-versus-titling", "name": "Text versus Titling", "description": "Keep Hoefler Titling outside this family's ownership while recording a supported relationship; the supplier presents the two as separate products. See [Hoefler Text catalogue](https://www.typography.com/fonts/hoefler-text/overview).", "questions": [ { "text": "Does the candidate belong to Hoefler Text, Hoefler Titling, or another family by the same designer?", "kind": "boundary", "id": "text-versus-titling-q01" }, { "text": "What documented relationship explains a proposed pairing without merging the two families?", "kind": "provenance", "id": "text-versus-titling-q02" } ] } ] } ] }, { "id": "faces-and-implementations", "name": "Faces and implementations", "description": "Record which Hoefler Text resources are actually available and how their implementations differ.", "rationale": "A family name cannot establish the available weights, styles, ornaments, or technical equivalence of two files.", "layers": [ { "id": "face-inventory", "name": "Face inventory", "description": "Establish supplied faces and their roles in composition.", "findings": [ { "id": "documented-face-selection", "name": "Documented face selection", "description": "Apple documents regular, italic, black, black italic, and ornaments identifiers; use these as implementation-specific evidence rather than a universal inventory. See [Apple font documentation](https://developer.apple.com/documentation/applenews/applying-apple-news-format-fonts).", "questions": [ { "text": "Which Hoefler Text faces does the acquired package actually contain?", "kind": "measurement", "id": "documented-face-selection-q01" }, { "text": "Does a bold or italic command select a supplied face, synthesize a style, or trigger substitution?", "kind": "action", "id": "documented-face-selection-q02" } ] } ] }, { "id": "implementation-comparison", "name": "Implementation comparison", "description": "Compare specific font resources rather than assuming all distributions behave alike.", "findings": [ { "id": "version-specific-equivalence", "name": "Version-specific equivalence", "description": "Record source and version alongside observed differences in naming, outlines, metrics, coverage, and layout features.", "questions": [ { "text": "What distributor, package, internal version, and fingerprint identify each compared resource?", "kind": "provenance", "id": "version-specific-equivalence-q01" }, { "text": "Which measured differences would prevent replacing one Hoefler Text resource with the other?", "kind": "boundary", "id": "version-specific-equivalence-q02" } ] } ] } ] }, { "id": "text-features-and-ornaments", "name": "Text features and ornaments", "description": "Assess Hoefler Text's usable typographic repertoire in a particular application.", "rationale": "Feature-rich typography requires evidence about both available glyphs and the application's ability to select them.", "layers": [ { "id": "typographic-feature-access", "name": "Typographic feature access", "description": "Inspect requested text features without assuming their presence in every implementation.", "findings": [ { "id": "verified-feature-behavior", "name": "Verified feature behavior", "description": "Test small capitals, ligatures, numeral forms, swashes, and other requested alternates individually; record absence or inaccessibility explicitly.", "questions": [ { "text": "Which requested Hoefler Text features exist in this font resource, and through which layout mechanism?", "kind": "measurement", "id": "verified-feature-behavior-q01" }, { "text": "Which application controls produce the intended glyph substitutions in rendered output?", "kind": "action", "id": "verified-feature-behavior-q02" }, { "text": "Are displayed small capitals supplied glyphs or scaled capitals generated by the application?", "kind": "boundary", "id": "verified-feature-behavior-q03" } ] } ] }, { "id": "ornament-selection", "name": "Ornament selection", "description": "Treat the associated ornaments as deliberately selected decorative glyphs.", "findings": [ { "id": "ornament-mapping-and-portability", "name": "Ornament mapping and portability", "description": "Inspect the acquired ornament resource's glyph mappings and output behavior before using it for decoration.", "questions": [ { "text": "Which glyph and character mapping produces the intended Hoefler Text ornament?", "kind": "measurement", "id": "ornament-mapping-and-portability-q01" }, { "text": "Does that ornament retain its appearance and intended decorative role through export and text extraction?", "kind": "action", "id": "ornament-mapping-and-portability-q02" } ] } ] } ] }, { "id": "composition-and-output", "name": "Composition and output", "description": "Evaluate whether the chosen Hoefler Text implementation works for the intended text and delivery medium.", "rationale": "Recognizing the family is insufficient to establish coverage, readable composition, or stable output.", "layers": [ { "id": "required-text-proof", "name": "Required-text proof", "description": "Test actual prose, punctuation, names, and numeric material.", "findings": [ { "id": "coverage-and-reading-proof", "name": "Coverage and reading proof", "description": "Judge the selected Hoefler Text faces using representative content at the proposed size, line length, and output resolution.", "questions": [ { "text": "Which required characters or combining sequences invoke fallback or fail to render correctly?", "kind": "measurement", "id": "coverage-and-reading-proof-q01" }, { "text": "At the intended text size, do the selected weight, italic, and numeral forms remain clear in representative passages?", "kind": "measurement", "id": "coverage-and-reading-proof-q02" } ] } ] }, { "id": "output-stability", "name": "Output stability", "description": "Check whether composition survives changes in renderer, machine, or delivery format.", "findings": [ { "id": "reflow-and-substitution-control", "name": "Reflow and substitution control", "description": "Compare fixed Hoefler Text specimens across target outputs and record reflow, clipping, lost features, and substituted faces.", "questions": [ { "text": "Which line endings, glyph choices, or bounding boxes change between the authoring view and delivered output?", "kind": "measurement", "id": "reflow-and-substitution-control-q01" }, { "text": "If Hoefler Text is unavailable at the destination, which fallback has been tested against the document's layout requirements?", "kind": "action", "id": "reflow-and-substitution-control-q02" } ] } ] } ] }, { "id": "acquisition-and-permitted-use", "name": "Acquisition and permitted use", "description": "Connect the specific Hoefler Text resource to its acquisition evidence and proposed deployment.", "rationale": "Installed availability, technical embeddability, and authorization for a particular use require separate evidence.", "layers": [ { "id": "distribution-record", "name": "Distribution record", "description": "Establish how the font resource entered the working environment.", "findings": [ { "id": "traceable-acquisition", "name": "Traceable acquisition", "description": "Retain the operating-system package, supplier delivery, or other documented acquisition record associated with the actual files.", "questions": [ { "text": "Was this Hoefler Text implementation acquired through an operating-system distribution, a supplier package, or another documented channel?", "kind": "provenance", "id": "traceable-acquisition-q01" }, { "text": "Which accompanying terms and version records apply to these particular files?", "kind": "provenance", "id": "traceable-acquisition-q02" } ] } ] }, { "id": "deployment-decision", "name": "Deployment decision", "description": "Evaluate a concrete output or distribution action against available evidence.", "findings": [ { "id": "action-specific-use-evidence", "name": "Action-specific use evidence", "description": "Record whether the intended document embedding, web serving, application bundling, or file transfer is supported technically and by applicable terms.", "questions": [ { "text": "What exact action will expose, embed, or distribute the Hoefler Text font resource?", "kind": "action", "id": "action-specific-use-evidence-q01" }, { "text": "Which applicable provision supports or restricts that action, and what remains unresolved?", "kind": "boundary", "id": "action-specific-use-evidence-q02" }, { "text": "Can the proposed delivery preserve the intended typography using a verified permitted method?", "kind": "action", "id": "action-specific-use-evidence-q03" } ] } ] } ] }, { "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-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This is a named typographic design, rather than an abstract concept; the supplied domain classification merits review.", "Check the specific distribution for its complete style inventory, character coverage and supported typographic features.", "These statements are recalled knowledge, not findings verified against sources in this response." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Hoefler Text this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-kinds", "name": "Kinds and varieties", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Regular", "Italic", "Black", "Black Italic" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Hoefler Text this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Book and editorial typography", "Long-form text composition", "Headings and display typography", "Typography using ligatures, small capitals and old-style numerals" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Hoefler Text this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Font substitution can change line breaks, pagination and the appearance of a document.", "Access to advanced typographic features depends on the font version and the application using it.", "Synthetic bold or italic styling can produce different results from the family's designed styles.", "Redistribution and embedding permissions depend on the applicable font licence." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Hoefler Text this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "name": "Serif typeface", "difference": "Serif typeface is a broad category; Hoefler Text is a particular named design within it." }, { "name": "Hoefler & Co.", "difference": "Hoefler & Co. is a type design company; Hoefler Text is a typeface family." }, { "name": "Jonathan Hoefler", "difference": "Jonathan Hoefler is the designer; Hoefler Text is one of his typeface designs." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Hoefler Text this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does an existing Vercy world model already own Hoefler Text, requiring this registry entry to link to it?", "Which authoritative historical records establish the family's attribution, initial release, and subsequent revisions?", "How do Apple-distributed and supplier-distributed implementations differ in face inventory, glyph coverage, metrics, and layout mechanisms?", "Which distinctive outline details provide reliable visual identification against commonly confused serif families?", "For the implementation ultimately selected, which language sequences, advanced features, ornament mappings, and deployment permissions can be verified?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 15, "questions": 27 } }