{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T10:12:20Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 17.2, "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: 01a09519-54af-7c90-bb16-7cf04cb10ad2\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: hatched map\nSense to describe: (none recorded)\nDomain code: INF.MED\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 043: 1001 reg", "usd": 0.0, "recall": true }, "codex": { "seconds": 80.2, "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: 01a09519-54a1-76b1-b777-98343ab2ffb2\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: hatched map\nRegistry id: vr.tr.hatched-map\nPlane / domain: INF / INF.MED\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\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", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:30+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q357674", "registryId": "vr.tr.hatched-map", "name": "hatched map", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.MED" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q357674/", "model": { "registry_id": "vr.tr.hatched-map", "name": "hatched map", "purpose": "Enable an agent to recognise a hatched map, assess how its relief strokes support terrain interpretation, and decide whether it can be compared, reproduced or transformed reliably.", "definition": "A hatched map, interpreted here as a hachure map, is a relief map that represents terrain slopes with short strokes oriented in the direction of steepest descent, using their weight or spacing to convey slope characteristics.", "scope_statement": "For vr.tr.hatched-map in INF / INF.MED, this draft models a cartographic representation using hachures to portray relief, including its encoding conventions, geographic reference, interpretive limits and relationships to editions and copies; the registry's intended boundary between map and representational technique remains to be confirmed.", "in_scope": [ "Identification of relief hachures and their distinction from unrelated map hatching", "Stroke conventions and their documented terrain meanings", "Geographic coverage, scale and registration of the relief portrayal", "Terrain evidence, cartographic generalisation and interpretive uncertainty", "Relationships among the map work, relief expression, edition and individual copy", "Conditions for reading, comparing, reproducing and transforming hachures" ], "out_of_scope": [ "The physical terrain and its current accessibility", "Complete modelling of surveys, elevation datasets or terrain-generation software", "Generic thematic area hatching without a relief function", "Complete inventories of roads, settlements and other base-map features", "Physical conservation of paper, printing plates and storage media", "General copyright law beyond applicable rights records linked to this map" ], "distinguishing_features": [ "The marks serve a terrain-relief function rather than merely filling thematic regions or decorating water.", "In conventional slope hachuring, strokes follow directions of greatest slope; this provides a recognition cue rather than a universal rule for every variant. See [OQLF terminology](https://vitrinelinguistique.oqlf.gouv.qc.ca/fiche-gdt/fiche/17086287/hachures).", "Relief interpretation depends on discrete strokes and their arrangement, distinguishing the portrayal from a continuous hillshade image.", "A contour-only map does not qualify unless a distinct hachure relief portrayal is also present.", "The registry label appears consistent with Wikidata's 'hatched map' entry, described as a mode of representing relief, but that does not establish the registry's external identifier. See [Wikidata Q357674](https://www.wikidata.org/wiki/Q357674)." ], "characteristics": [ { "name": "Relief-hatching role", "kind": "category", "unit_or_values": "principal relief method | supplementary relief method | uncertain", "why_it_matters": "Determines whether hachures define the representation or support another relief method." }, { "name": "Documented hachure convention", "kind": "relation", "unit_or_values": "Linked legend, cartographic instruction or attributed convention; unknown permitted", "why_it_matters": "Provides the basis for assigning meaning to stroke differences." }, { "name": "Stroke orientation rule", "kind": "category", "unit_or_values": "slope-following | other documented rule | mixed | unknown", "why_it_matters": "Controls whether stroke direction supports a terrain-direction inference." }, { "name": "Stroke-weight and spacing semantics", "kind": "category", "unit_or_values": "Record meanings separately for width, spacing, length and darkness; undocumented permitted", "why_it_matters": "Prevents treating visual variation as a calibrated terrain measurement without evidence." }, { "name": "Nominal map scale", "kind": "measurement", "unit_or_values": "Representative fraction 1:n, variable scale or unknown; identify the edition", "why_it_matters": "Constrains the detail represented and distinguishes original scale from screen magnification." }, { "name": "Geographic reference", "kind": "relation", "unit_or_values": "Linked footprint, coordinate reference system and registration evidence, with unknown components explicit", "why_it_matters": "Supports spatial comparison without silently assuming modern coordinates." }, { "name": "Relief evidence lineage", "kind": "relation", "unit_or_values": "Linked surveys, observations, predecessor maps or elevation datasets with dates and attribution confidence", "why_it_matters": "Separates the age and quality of terrain evidence from publication date." }, { "name": "Hachure legibility", "kind": "state", "unit_or_values": "readable | partly merged | partly lost | obscured | unassessed, by region and copy", "why_it_matters": "Identifies where reproduction or damage prevents reliable interpretation." }, { "name": "Quantitative interpretability", "kind": "state", "unit_or_values": "qualitative only | documented classes | calibrated relationship | unknown", "why_it_matters": "Sets the permitted precision of slope or elevation claims." }, { "name": "Representation identity", "kind": "relation", "unit_or_values": "Linked map work, relief expression, edition, sheet and physical or digital item", "why_it_matters": "Prevents attributing a scan defect or revised hachure pattern to every version of the map." } ], "affordances": [ "Identify probable relief hachures and record the evidence supporting that classification.", "Describe terrain form to the degree supported by the map's documented convention.", "Compare hachure patterns across editions or against independently referenced terrain evidence.", "Annotate ambiguous, illegible or conflicting relief regions.", "Reproduce or rescale the portrayal while checking stroke survival and applicable rights.", "Create a georeferenced or vector derivative with explicit transformation history and interpretation limits." ], "agent_conduct": { "may": [ "Identify hachures on a map and describe the terrain they show within the map's convention.", "Compare editions of a hachure map with modern elevation data." ], "must_not": [ "Use a historic hachure map for navigation in dangerous terrain without current maps.", "Reproduce maps in breach of the rights holder's terms.", "Present hachure-derived slopes as precise elevation measurements." ], "requires_human": [ "Publishing digitized reproductions of maps held by archives." ] }, "ethics": { "considerations": [ "Historic maps preserve knowledge of landscapes and the people who surveyed them.", "Outdated maps can mislead people in mountains." ], "affected_parties": [ "Map users", "Archives and libraries", "Hikers" ] }, "owners": { "steward": "The holding archive or library for each sheet; rights holders for recent editions.", "master_systems": [ "Library and archive map catalogues" ] }, "visual_identification": [ "Fine short strokes drawn down the slope direction, denser or bolder where terrain is steeper.", "Usually without contour lines, giving a shaded, engraved look to hills." ], "failure_modes_and_hazards": [ "No absolute heights can be read, which leads to misjudged terrain.", "Fine strokes can be lost in low-resolution copies." ], "what_it_is_for": [ "Hachure maps occur in historical atlases, topographic surveys and terrain illustrations.", "Their strokes help readers interpret slope direction and relative steepness where relief is represented without explicit elevation contours.", "They support historical landscape comparison, although quantitative interpretation depends on the map's documented drawing conventions." ], "facets_not_applicable": { "interfaces": "No specific standard or regulation applies universally to hachure relief depiction itself." } }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q357674: hatched map", "url": "https://www.wikidata.org/wiki/Q357674", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Hachure map", "url": "https://en.wikipedia.org/wiki/Hachure_map", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "relief-identity", "name": "Relief identity", "description": "Establish what qualifies as the registered thing and which marks perform its relief function.", "rationale": "Hatching appears in many map contexts, so recognition must establish meaning rather than rely on texture alone.", "layers": [ { "id": "entry-interpretation", "name": "Entry interpretation", "description": "Resolve the relationship between the registry label, a relief technique and maps using it.", "findings": [ { "id": "map-technique-boundary", "name": "Map-technique boundary", "description": "Record whether the catalogued subject is a map representation or the hachuring technique, retaining the registry entry without creating an unsupported split.", "questions": [ { "text": "What registry evidence establishes whether this entry denotes maps using hachures or the technique itself?", "kind": "definition", "id": "map-technique-boundary-q01" }, { "text": "Does an existing Vercy map or relief model already own this concept?", "kind": "boundary", "id": "map-technique-boundary-q02" } ] } ] }, { "id": "mark-classification", "name": "Mark classification", "description": "Separate relief strokes from visually similar symbols and identify mixed portrayals.", "findings": [ { "id": "relief-function-evidence", "name": "Relief-function evidence", "description": "Require a legend, documented convention or qualified visual interpretation to classify strokes as relief hachures.", "questions": [ { "text": "Which evidence shows that these strokes portray relief rather than land cover, water or administrative categories?", "kind": "definition", "id": "relief-function-evidence-q01" }, { "text": "Are hachures the principal relief portrayal or combined with contours, elevation tints or hillshade?", "kind": "boundary", "id": "relief-function-evidence-q02" } ] } ] } ] }, { "id": "hachure-semantics", "name": "Hachure semantics", "description": "Capture the rules connecting stroke geometry and visual weight to terrain interpretation.", "rationale": "An agent needs an explicit reading convention before deriving meaning from stroke direction or darkness.", "layers": [ { "id": "direction-and-arrangement", "name": "Direction and arrangement", "description": "Describe how stroke orientation and grouping participate in relief portrayal.", "findings": [ { "id": "orientation-rule", "name": "Orientation rule", "description": "Record the applicable direction rule and exceptions, without assuming that a stroke alone identifies which end is downhill.", "questions": [ { "text": "What documented relationship connects stroke orientation to terrain slope?", "kind": "definition", "id": "orientation-rule-q01" }, { "text": "What additional evidence distinguishes uphill from downhill and ridges from valleys?", "kind": "measurement", "id": "orientation-rule-q02" } ] } ] }, { "id": "visual-weight", "name": "Visual weight", "description": "Distinguish the meanings of width, spacing, length and darkness.", "findings": [ { "id": "encoding-calibration", "name": "Encoding calibration", "description": "Treat each visual variable as uncalibrated until the map's convention supports a specific interpretation.", "questions": [ { "text": "Which stroke variables encode slope, illumination or another documented property?", "kind": "definition", "id": "encoding-calibration-q01" }, { "text": "Does the evidence support qualitative ordering, discrete classes or a numerical relationship?", "kind": "measurement", "id": "encoding-calibration-q02" }, { "text": "Where do overlaps, lettering or printing variation prevent that relationship from being read?", "kind": "boundary", "id": "encoding-calibration-q03" } ] } ] } ] }, { "id": "spatial-and-terrain-evidence", "name": "Spatial and terrain evidence", "description": "Connect the relief portrayal to its geographic frame and underlying terrain information.", "rationale": "Hachures cannot be compared meaningfully without knowing their spatial reference and evidential origin.", "layers": [ { "id": "geographic-frame", "name": "Geographic frame", "description": "Record coverage, scale, orientation and spatial registration.", "findings": [ { "id": "spatial-reference", "name": "Spatial reference", "description": "Distinguish the original map reference from coordinates assigned to a later digital copy.", "questions": [ { "text": "What area, nominal scale, orientation and coordinate reference are documented for this sheet or edition?", "kind": "measurement", "id": "spatial-reference-q01" }, { "text": "Which control points and residual errors support a later georeferencing transformation?", "kind": "provenance", "id": "spatial-reference-q02" } ] } ] }, { "id": "terrain-lineage", "name": "Terrain lineage", "description": "Trace the observations and cartographic decisions behind the strokes.", "findings": [ { "id": "evidence-and-generalisation", "name": "Evidence and generalisation", "description": "Record terrain sources and known simplifications separately from the date and appearance of the published map.", "questions": [ { "text": "Which observations, surveys, predecessor maps or elevation datasets informed these hachures, and when?", "kind": "provenance", "id": "evidence-and-generalisation-q01" }, { "text": "What evidence identifies omitted, exaggerated or simplified terrain features?", "kind": "boundary", "id": "evidence-and-generalisation-q02" }, { "text": "Which relief regions have unknown or conflicting source histories?", "kind": "provenance", "id": "evidence-and-generalisation-q03" } ] } ] } ] }, { "id": "versions-and-reproduction", "name": "Versions and reproduction", "description": "Track which relief expression is being inspected and how copying affects its strokes.", "rationale": "A revised engraving, reduced print and low-resolution scan may support different readings of the same map work.", "layers": [ { "id": "relief-version-identity", "name": "Relief version identity", "description": "Relate map works, changed relief expressions, editions and inspected items.", "findings": [ { "id": "hachure-revision-lineage", "name": "Hachure revision lineage", "description": "Distinguish substantive changes to the relief portrayal from changes in printing, carrier or digitisation.", "questions": [ { "text": "Which work, edition, sheet and item does the inspected hachure portrayal belong to?", "kind": "provenance", "id": "hachure-revision-lineage-q01" }, { "text": "Were strokes redrawn or corrected, or does the apparent difference arise from reproduction?", "kind": "boundary", "id": "hachure-revision-lineage-q02" } ] } ] }, { "id": "stroke-preservation", "name": "Stroke preservation", "description": "Assess whether the inspected manifestation preserves the visual distinctions needed for reading.", "findings": [ { "id": "reproduction-fidelity", "name": "Reproduction fidelity", "description": "Assess merged lines, missing fine strokes, contrast shifts and local distortion at the intended viewing scale.", "questions": [ { "text": "At what reproduction size or image resolution do necessary stroke distinctions become unreadable?", "kind": "measurement", "id": "reproduction-fidelity-q01" }, { "text": "Which regions show stroke loss, merging, damage or distortion relative to the best available reference?", "kind": "measurement", "id": "reproduction-fidelity-q02" }, { "text": "Who created or revised the relief portrayal and digital reproduction, and which recorded rights apply to the proposed reuse?", "kind": "action", "id": "reproduction-fidelity-q03" } ] } ] } ] }, { "id": "interpretation-and-derivation", "name": "Interpretation and derivation", "description": "Set evidence-based limits on reading terrain and creating derived representations.", "rationale": "Recognisable relief does not by itself justify numerical reconstruction or unrestricted transformation.", "layers": [ { "id": "supported-terrain-readings", "name": "Supported terrain readings", "description": "State what the particular map permits an agent to infer.", "findings": [ { "id": "inference-limits", "name": "Inference limits", "description": "Attach confidence and supporting evidence to terrain interpretations, keeping numerical claims conditional on calibration.", "questions": [ { "text": "Which landform or relative-steepness interpretations are supported by the convention and legibility of this region?", "kind": "measurement", "id": "inference-limits-q01" }, { "text": "What independent evidence would be required before reporting a slope angle or elevation?", "kind": "boundary", "id": "inference-limits-q02" }, { "text": "Where should an agent abstain from interpretation because marks or conventions are ambiguous?", "kind": "action", "id": "inference-limits-q03" } ] } ] }, { "id": "derived-relief-products", "name": "Derived relief products", "description": "Control transformations that may alter or overinterpret the hachure portrayal.", "findings": [ { "id": "transformation-validation", "name": "Transformation validation", "description": "Preserve traceability when georeferencing, resampling, tracing or converting strokes into another relief representation.", "questions": [ { "text": "Which proposed transformations preserve the documented meanings of stroke direction, spacing and weight?", "kind": "action", "id": "transformation-validation-q01" }, { "text": "How will the derivative be checked for lost strokes, false connections and spatial distortion?", "kind": "measurement", "id": "transformation-validation-q02" }, { "text": "How will inferred terrain content be distinguished from marks directly transcribed from the source map?", "kind": "provenance", "id": "transformation-validation-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": [ "The registry provides no sense; verify whether 'hatched map' means a relief hachure map or a thematic map using hatched fills.", "The established cartographic term for the relief interpretation is 'hachure map'; the definition and kinds here depend on that interpretation.", "No sources were consulted, and no specific identifiers or governing standards are asserted." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of hatched map 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": [ "Slope hachure maps", "Shadow hachure maps" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of hatched map 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": [ "Representing terrain relief on historical topographic and military maps", "Showing the orientation and relative steepness of slopes", "Supporting interpretation of historical cartographic representations of terrain" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of hatched map 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": [ "Stroke density and thickness can obscure labels and other map features.", "Hachures alone generally do not provide precise elevations.", "Different hachuring conventions can lead readers to misinterpret slope steepness.", "Reproduction or reduction can merge fine strokes and degrade terrain legibility.", "Shadow hachures can make visual darkness reflect assumed illumination as well as terrain slope." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of hatched map 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": "Contour map", "difference": "Contours connect points of equal elevation; relief hachures generally follow the direction of steepest descent." }, { "name": "Shaded relief map", "difference": "Shaded relief represents terrain through tonal shading under an assumed light source rather than discrete hachure strokes." }, { "name": "Hypsometric tint map", "difference": "Hypsometric tints encode elevation bands using colour rather than encoding slope through strokes." }, { "name": "Pattern-filled thematic map", "difference": "Hatched area fills can encode thematic categories or values without representing terrain; this is a distinct possible meaning of 'hatched map'." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of hatched map this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does vr.tr.hatched-map correspond to Wikidata Q357674, and does the registry intend a map type, a relief expression or a cartographic technique?", "Does an existing Vercy world model already cover hachure relief mapping, requiring linkage rather than a separate publication?", "Which historical and contemporary hachure conventions belong within this entry, particularly variants that depart from slope-following strokes?", "What evidence and validation thresholds would justify quantitative interpretation for any particular convention?", "Which reference maps and editions should establish practical criteria for stroke legibility, reproduction fidelity and mixed-method relief classification?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 15, "questions": 30 } }