{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T11:02:03Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 28.4, "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: 01a09546-feda-7171-8d6a-6bebbbfe86e6\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: long-distance cycling route\nSense to describe: (none recorded)\nDomain code: PHY.BLT\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Bat", "usd": 0.0, "recall": true }, "codex": { "seconds": 71.0, "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: 01a09546-fee6-7273-8993-dd954630d22b\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: long-distance cycling route\nRegistry id: vr.tr.long-distance-cycling-route\nPlane / domain: PHY / PHY.BLT\nRegistry definition: (none recorded)\nNames f" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-05T23:59:00Z", "ingestedAt": "2026-10-05T20:56:54+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-Q353027", "registryId": "vr.tr.long-distance-cycling-route", "name": "long-distance cycling route", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.BLT" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q353027/", "model": { "registry_id": "vr.tr.long-distance-cycling-route", "name": "long-distance cycling route", "purpose": "Enable an agent to identify a long-distance cycling route, assess its continuity and suitability for a proposed journey, and determine which sections may be ridden under current conditions.", "definition": "A long-distance cycling route is an identified, connected itinerary intended for extended bicycle journeys, usually over multiple days, following roads, cycleways, tracks or a combination of these rather than necessarily constituting a single purpose-built facility.", "scope_statement": "This model owns the identity, connected alignment, cycling conditions, navigation, access constraints and operational state of an extended cycling route, including its relationships to underlying infrastructure and journey-support services without owning those assets.", "in_scope": [ "Route identity, intended cycling use and evidence for its long-distance classification", "Ordered sections, endpoints, junctions, branches and designated alternatives", "Surface, gradients, traffic exposure and barriers affecting cycling continuity", "Wayfinding, mapped alignment and discrepancies between published and ground conditions", "Section-specific access, closures, diversions and maintenance responsibility", "Spacing and availability of services needed to plan extended cycling journeys" ], "out_of_scope": [ "Engineering and asset management of individual roads, bridges and cycleways", "The wider cycling network except where it connects to or contains this route", "An individual rider's itinerary, activity record or fitness profile", "Cycle races, organised tours and other events using the route", "Ownership and internal operations of accommodation, shops and transport operators", "Bicycle design, maintenance and equipment inventories" ], "distinguishing_features": [ "Represents an identifiable connected cycling course with defined endpoints or a loop, rather than an unordered collection of cycling facilities.", "Its long-distance classification requires recorded designation or an explicit classification basis; length alone is not assigned a universal threshold.", "Retains an identity across journeys and riders, distinguishing it from a person's one-off itinerary or recorded ride.", "May combine roads, dedicated cycleways, tracks and transfer links, so it is not equivalent to a single physically segregated cycleway.", "Describes a course intended for cycling independently of any event that temporarily uses it." ], "characteristics": [ { "name": "Route identity and designation", "kind": "category", "unit_or_values": "Name, identifier, designation scheme and classification basis", "why_it_matters": "Distinguishes the route from similarly named trails, promotional itineraries and overlapping routes." }, { "name": "Alignment and section order", "kind": "relation", "unit_or_values": "Ordered connections between georeferenced sections, junctions and transfer links", "why_it_matters": "Establishes whether the route forms a traversable course and which alternatives belong to it." }, { "name": "Route length", "kind": "measurement", "unit_or_values": "Kilometres, with alignment version, selected branch and treatment of transfers", "why_it_matters": "Supports journey planning and makes conflicting published distances interpretable." }, { "name": "Elevation and gradient profile", "kind": "measurement", "unit_or_values": "Elevation and cumulative ascent in metres; section gradients in percent; direction and calculation method", "why_it_matters": "Reveals climbing demand and sections that may constrain loaded or adapted cycles." }, { "name": "Surface and effective riding width", "kind": "category", "unit_or_values": "Section-specific surface classes, condition descriptions and width measurements where available", "why_it_matters": "Helps assess bicycle compatibility, passing space and weather sensitivity." }, { "name": "Motor-traffic exposure", "kind": "category", "unit_or_values": "Separated, shared road, crossing or mixed; supported by section-specific traffic evidence", "why_it_matters": "Distinguishes route designation from the actual conditions a rider encounters." }, { "name": "Cycling access status", "kind": "state", "unit_or_values": "Permitted, conditional, prohibited or unknown, by section, cycle class and time", "why_it_matters": "Prevents a mapped connection from being treated as permission to ride." }, { "name": "Operational continuity", "kind": "state", "unit_or_values": "Verified continuous, interrupted, diversion available, planned or unverified; dated by section", "why_it_matters": "Separates the intended route from what can currently be traversed." }, { "name": "Wayfinding coverage", "kind": "state", "unit_or_values": "Physical signs and digital guidance coverage, consistency and verification date", "why_it_matters": "Shows where riders may need additional navigation support." }, { "name": "Essential-service gaps", "kind": "measurement", "unit_or_values": "Kilometres along the selected alignment between verified water, food, accommodation or repair opportunities", "why_it_matters": "Identifies stretches requiring advance provisioning or different stage boundaries." } ], "affordances": [ "Trace a selected route variant and identify gaps, transfers or disconnected sections.", "Assess section suitability for a specified cycle type, rider capability and travel date.", "Propose stage boundaries using distance, climbing and verified service availability.", "Locate lawful alternatives around closures or unsuitable sections while distinguishing official diversions from suggestions.", "Compare mapped guidance with signs and field reports, and flag discrepancies for review.", "Identify the responsible contact for a route defect, access uncertainty or navigation problem." ], "agent_conduct": { "may": [ "Plan a multi-day journey along a cycling route and report section closures and conditions from official sources.", "Assess whether each section suits the rider's stated bicycle, load and experience." ], "must_not": [ "Route riders onto motorways, private land or closed sections.", "Present an unsigned or proposed route as open and continuous.", "Share a rider's live location with others without consent.", "Understate traffic, terrain or weather risks on a section." ], "requires_human": [ "Directing riders onto a detour through busy traffic when a section closes." ] }, "ethics": { "considerations": [ "Route choices decide how exposed cyclists are to motor traffic.", "Routes pass through communities and protected landscapes that deserve respect." ], "affected_parties": [ "Cyclists", "Residents along the route", "Landowners" ] }, "owners": { "steward": "The route's managing body or the road and path authorities for each section.", "master_systems": [] }, "visual_identification": [ "Route signs with a consistent name, number or symbol at junctions.", "Distance and direction markers placed along roads and cycleways.", "Information boards at route starts and towns along the way." ], "failure_modes_and_hazards": [ "Gaps or unsigned sections that send riders into heavy traffic.", "Closed or damaged sections not reflected in route information.", "Remote stretches with no water, shelter or help in bad weather." ], "what_it_is_for": [ "Long-distance cycling routes support bicycle tourism and extended journeys between towns, regions or countries.", "They connect sections of roads, cycleways and tracks through a named or otherwise identified itinerary.", "Journey planning uses section-level information about surface, access, gradients, services and seasonal interruptions." ], "standards_and_regulation": [ "The Manual on Uniform Traffic Control Devices, issued by the United States Federal Highway Administration, governs applicable traffic signs and markings on route sections open to public travel within its jurisdiction." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q353027: long-distance cycling route", "url": "https://www.wikidata.org/wiki/Q353027", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Long-distance cycling route", "url": "https://en.wikipedia.org/wiki/Long-distance_cycling_route", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "route-identity-and-extent", "name": "Route identity and extent", "description": "Establishes what course the route name denotes and why it belongs in this class.", "rationale": "A long-distance cycling route needs a stable identity despite shared infrastructure, variants and changing alignments.", "layers": [ { "id": "designation-and-purpose", "name": "Designation and purpose", "description": "Records the route's identifying evidence, intended cycling use and classification basis.", "findings": [ { "id": "recognised-cycling-course", "name": "Recognised cycling course", "description": "Establish whether the name denotes a maintained or documented route rather than an individual journey suggestion.", "questions": [ { "text": "What evidence establishes this route's name, identifier, intended cycling use and long-distance classification?", "kind": "provenance", "id": "recognised-cycling-course-q01" }, { "text": "What distinguishes this route from a touring itinerary, a cycleway asset or a larger route network?", "kind": "boundary", "id": "recognised-cycling-course-q02" } ] } ] }, { "id": "endpoints-and-variants", "name": "Endpoints and variants", "description": "Defines the route's geographic extent and the identity of branches and alternatives.", "findings": [ { "id": "canonical-route-extent", "name": "Canonical route extent", "description": "Resolve the main course, loop closure and variants before assigning route-wide measurements.", "questions": [ { "text": "Which endpoints or loop closure define the route, and which branches are included in its identity?", "kind": "definition", "id": "canonical-route-extent-q01" }, { "text": "Which alternatives are designated parts of this route, and which belong to separate connecting routes?", "kind": "boundary", "id": "canonical-route-extent-q02" } ] } ] } ] }, { "id": "alignment-and-continuity", "name": "Alignment and continuity", "description": "Describes the ordered course and whether its connections support through travel.", "rationale": "An extended route can appear continuous on a map while containing missing links, transfers or direction-dependent connections.", "layers": [ { "id": "section-topology", "name": "Section topology", "description": "Connects riding sections, junctions and direction-dependent links into a traceable alignment.", "findings": [ { "id": "traceable-section-chain", "name": "Traceable section chain", "description": "Establish an ordered alignment whose length and connectivity can be checked.", "questions": [ { "text": "Which ordered sections and junctions form the selected alignment in each permitted direction?", "kind": "definition", "id": "traceable-section-chain-q01" }, { "text": "What is its measured length, and which alignment version, branches and measurement method produce that value?", "kind": "measurement", "id": "traceable-section-chain-q02" } ] } ] }, { "id": "gaps-and-transfers", "name": "Gaps and transfers", "description": "Identifies breaks in cycling continuity and any required non-cycling movement.", "findings": [ { "id": "through-journey-feasibility", "name": "Through-journey feasibility", "description": "Expose unbuilt sections, dismount requirements and transfer dependencies instead of concealing them in a continuous line.", "questions": [ { "text": "Where does the alignment require dismounting, carrying a cycle, using transport or crossing an uncompleted link?", "kind": "boundary", "id": "through-journey-feasibility-q01" }, { "text": "What verified connection or alternative permits onward travel, including any cycle-carriage or operating-time conditions?", "kind": "action", "id": "through-journey-feasibility-q02" } ] } ] } ] }, { "id": "cycling-demand-and-exposure", "name": "Cycling demand and exposure", "description": "Characterises the physical demands and riding environment section by section.", "rationale": "Route-wide labels can conceal short sections that determine whether a long journey is feasible for a particular rider and cycle.", "layers": [ { "id": "terrain-surface-and-barriers", "name": "Terrain, surface and barriers", "description": "Records climbing, surface conditions and physical restrictions relevant to cycle passage.", "findings": [ { "id": "cycle-specific-passability", "name": "Cycle-specific passability", "description": "Assess passage using observed dimensions and conditions rather than a single unsupported difficulty label.", "questions": [ { "text": "What gradients, sustained climbs, surface conditions and constrained widths occur along each section?", "kind": "measurement", "id": "cycle-specific-passability-q01" }, { "text": "Which gates, steps, tight turns or other barriers constrain loaded bicycles, trailers, tandems or adapted cycles?", "kind": "boundary", "id": "cycle-specific-passability-q02" } ] } ] }, { "id": "traffic-and-weather-exposure", "name": "Traffic and weather exposure", "description": "Locates interactions with vehicles and environmental conditions that alter riding suitability.", "findings": [ { "id": "section-exposure-profile", "name": "Section exposure profile", "description": "Identify demanding road interactions and condition-dependent hazards with dated supporting evidence.", "questions": [ { "text": "Where are shared-road sections and difficult crossings, and what evidence describes traffic speed, volume and separation?", "kind": "measurement", "id": "section-exposure-profile-q01" }, { "text": "Which sections become unsuitable under flooding, snow, heat, wind or surface deterioration, and what evidence supports that assessment?", "kind": "provenance", "id": "section-exposure-profile-q02" } ] } ] } ] }, { "id": "access-navigation-and-route-care", "name": "Access, navigation and route care", "description": "Connects permission to ride with usable guidance and current operational information.", "rationale": "Designation, legal access, signage and maintenance may be managed by different parties across a long route.", "layers": [ { "id": "permissions-and-operating-state", "name": "Permissions and operating state", "description": "Tracks section-specific access conditions, closures and responsibility for operational updates.", "findings": [ { "id": "dated-access-and-diversion-status", "name": "Dated access and diversion status", "description": "Establish where cycling is allowed and what action is justified when the intended alignment is unavailable.", "questions": [ { "text": "Which authorities or land managers establish access conditions, including restrictions by season, direction or cycle class?", "kind": "provenance", "id": "dated-access-and-diversion-status-q01" }, { "text": "For a closure or access restriction, what dated notice and verified diversion determine where a rider may proceed?", "kind": "action", "id": "dated-access-and-diversion-status-q02" }, { "text": "Who receives reports about defects, access conflicts and missing links on each affected section?", "kind": "action", "id": "dated-access-and-diversion-status-q03" } ] } ] }, { "id": "signs-and-digital-guidance", "name": "Signs and digital guidance", "description": "Assesses whether riders can follow the intended alignment using published and on-ground information.", "findings": [ { "id": "navigation-consistency", "name": "Navigation consistency", "description": "Record guidance coverage and resolve disagreement between route files, maps and signs.", "questions": [ { "text": "Which maps, route files and sign systems describe the alignment, and when were they last verified?", "kind": "provenance", "id": "navigation-consistency-q01" }, { "text": "Where do signs and digital guidance disagree, and what evidence should guide an alignment correction?", "kind": "action", "id": "navigation-consistency-q02" } ] } ] } ] }, { "id": "extended-journey-support", "name": "Extended journey support", "description": "Relates the route to provisioning, overnight stops and opportunities to enter or leave the course.", "rationale": "Long-distance cycling requires understanding service gaps and escape options beyond the rideability of individual sections.", "layers": [ { "id": "provisioning-and-stage-options", "name": "Provisioning and stage options", "description": "Locates essential services and plausible stopping areas without prescribing a single itinerary.", "findings": [ { "id": "supported-stage-planning", "name": "Supported stage planning", "description": "Make service spacing and availability usable alongside distance and climbing demand.", "questions": [ { "text": "What are the longest verified gaps between drinking water, food, overnight accommodation and cycle-repair opportunities?", "kind": "measurement", "id": "supported-stage-planning-q01" }, { "text": "Which stage boundaries are feasible for a stated daily distance and climbing limit, given service opening periods and access detours?", "kind": "action", "id": "supported-stage-planning-q02" } ] } ] }, { "id": "entry-exit-and-assistance", "name": "Entry, exit and assistance", "description": "Identifies ways to join, leave or obtain help along remote or demanding sections.", "findings": [ { "id": "journey-interruption-options", "name": "Journey interruption options", "description": "Assess practical alternatives when a rider cannot continue along the planned course.", "questions": [ { "text": "Where can riders enter or leave the route using connecting roads or transport with verified cycle-carriage arrangements?", "kind": "action", "id": "journey-interruption-options-q01" }, { "text": "Which sections have limited assistance access or communications coverage, and how recently was that information checked?", "kind": "provenance", "id": "journey-interruption-options-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-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This describes the general route type because no narrower sense is recorded.", "There is no universally accepted distance threshold; length alone does not establish designation, continuity or suitability.", "Certification, completion status, access rights and current surface conditions require checking for any specific route; naming a standard does not imply compliance." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of long-distance cycling route 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": [ "International touring routes", "National touring routes", "Regional touring routes", "Long-distance off-road routes", "Themed heritage or landscape routes", "Long-distance circular routes" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of long-distance cycling route this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "scheme": "EuroVelo route numbering", "value_or_pattern": "EV followed by a route number", "note": "Identifies routes within the European Cyclists' Federation's EuroVelo network, not long-distance cycling routes generally." }, { "scheme": "UK National Cycle Network route numbering", "value_or_pattern": "National Cycle Route followed by a number", "note": "A network route identifier; inclusion does not by itself establish that a route is long-distance." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of long-distance cycling route this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "European Certification Standard, developed by the European Cyclists' Federation for assessing long-distance cycle routes.", "Applicable national and local traffic rules, access restrictions and traffic-sign regulations govern the individual roads and paths used." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of long-distance cycling route 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": [ "Multi-day cycle touring and bicycle holidays", "Connecting settlements, accommodation and visitor attractions", "Supporting regional tourism and local businesses", "Providing sections used for everyday transport and shorter recreational rides", "Organising supported tours and endurance journeys" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of long-distance cycling route this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "quantity": "Total route length", "typical_range": "Hundreds to several thousand; the category has no universal minimum length", "unit": "km" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of long-distance cycling route 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": [ "Discontinuities, closures or missing crossings that make the intended itinerary impassable", "Exposure to fast or heavy motor traffic and unsafe junctions", "Surfaces, gradients or barriers unsuitable for a rider's bicycle, load or abilities", "Missing or inconsistent wayfinding and outdated route information", "Remote sections with insufficient water, shelter, repair services or emergency access" ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of long-distance cycling route this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Route designation, numbering and signage differ between countries and network operators.", "Some networks primarily use paved roads and separated cycleways, while others include gravel roads and trails.", "Public access rights, seasonal availability and rules for electrically assisted bicycles vary by jurisdiction and segment." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of long-distance cycling route 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": "Cycleway", "difference": "A cycleway is a physical facility for cycling; a long-distance route is an itinerary that may use many facilities and ordinary roads." }, { "name": "Cycle route network", "difference": "A network comprises interconnected routes; one long-distance route is an identified itinerary within or across networks." }, { "name": "Bicycle touring", "difference": "Bicycle touring is an activity; the route is an itinerary available for that activity." }, { "name": "Cycling race course", "difference": "A race course is defined for a competitive event; a long-distance cycling route need not host competition." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of long-distance cycling route this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "What operational definition of long-distance should this registry use when no recognised designation or minimum distance is recorded?", "Does an existing Vercy world model already cover this concept and therefore provide the authoritative publication?", "Should an undocumented but regularly used cycling course qualify, and what evidence would establish its identity independently of individual itineraries?", "How should planned sections, seasonal transfers and prolonged closures affect whether a route is described as continuous?", "Which section-assessment methods and evidence freshness requirements should govern claims about cycle compatibility, traffic exposure and service availability?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 19, "questions": 30 } }