{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T10:41:27Z", "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: 01a09534-50d0-74c0-8625-68739f0dd77c\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: junction\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 043: 1001 regist", "usd": 0.0, "recall": true }, "codex": { "seconds": 58.9, "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: 01a09534-50d7-7562-bacc-5657ac9d4619\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: junction\nRegistry id: vr.tr.junction\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nContex" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-05T23:50:00Z", "ingestedAt": "2026-10-05T20:47:14+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "standards_and_regulation", "visual_identification" ] }, "revisions": [ { "at": "2026-10-07T11:15:55+00:00", "engine": "codex", "fields": [ "agent_conduct", "definition", "distinguishing_features", "ethics", "failure_modes_and_hazards", "in_scope", "out_of_scope", "purpose", "scope_statement", "visual_identification" ], "answering_review": "2c97669a520c05f05e7520a549107a8484e317f5a314f2925b0a87f3ba55bed4" } ], "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T12:16:29+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q1777515", "registryId": "vr.tr.junction", "name": "junction", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q1777515/", "model": { "registry_id": "vr.tr.junction", "name": "junction", "purpose": "Enable an agent to recognise a traffic junction, record the routes, directions or modes it connects, assess its usability, and determine which movements and interactions are permitted.", "definition": "A junction is a location where traffic can change between different routes, directions, or sometimes modes of travel.", "scope_statement": "This model owns a junction as a bounded transport location where traffic can change routes, directions or sometimes modes, including its local connections, permitted movements, operating state and access constraints.", "in_scope": [ "The physical area where traffic routes connect or travel directions or modes can change.", "Connected routes, access points and local transport topology.", "Permitted movements and transfers between routes, directions or modes.", "Local traffic controls, separation arrangements and operating states.", "Condition and constraints that affect the junction's usability." ], "out_of_scope": [ "The full transport networks containing the junction.", "The complete roads, tracks, paths or waterways connected by the junction.", "Vehicles and travellers considered independently of their interaction with the junction.", "Abstract graph vertices without a physical transport referent.", "Electrical connections, pipe joints and structural joints.", "Network-wide scheduling, optimisation and operating policy." ], "distinguishing_features": [ "Identify a bounded location where traffic can change routes, directions or modes; proximity alone does not establish a junction.", "Establish an actual transport connection; a crossing with no possible movement between the crossing routes is not a junction between them.", "Distinguish the junction area from equipment that merely supports, controls or labels it.", "Record the available movements and whether they involve merging, branching, turning or changing modes.", "Distinguish a junction instance from a junction design or diagram symbol." ], "characteristics": [ { "name": "Junction sense", "kind": "category", "unit_or_values": "transport | electrical | fluid | mechanical | other specified | unresolved", "why_it_matters": "Determines which connection tests, measurements, and allowable actions are meaningful." }, { "name": "Incident elements", "kind": "relation", "unit_or_values": "References to connected physical elements, with locally identified interfaces", "why_it_matters": "Establishes what the junction connects and prevents confusion with adjacent connections." }, { "name": "Interface count", "kind": "measurement", "unit_or_values": "Count of interfaces under an explicitly stated counting convention", "why_it_matters": "Describes local connection complexity without treating lanes, terminals, or branches as interchangeable." }, { "name": "Connection topology", "kind": "relation", "unit_or_values": "Interface pairs or groups that are physically connected, including direction where applicable", "why_it_matters": "Shows which routes or transfers exist rather than assuming all incident elements connect to one another." }, { "name": "Transfer or coupling mode", "kind": "category", "unit_or_values": "movement | fluid passage | electrical conduction | force transmission | other specified", "why_it_matters": "Defines what continuity means for this junction." }, { "name": "Physical extent", "kind": "measurement", "unit_or_values": "Domain-appropriate dimensions in m or mm, or a spatial boundary with coordinate reference", "why_it_matters": "Separates the junction region from its incident elements and nearby junctions." }, { "name": "Connection state", "kind": "state", "unit_or_values": "Per connection: established | interrupted | restricted | unknown; domain-specific substates where supported", "why_it_matters": "Supports judgments about whether an intended interaction is currently possible." }, { "name": "Operating limits", "kind": "measurement", "unit_or_values": "Domain-specific limits with units, applicability conditions, and evidence; unknown where unverified", "why_it_matters": "Prevents an agent from inferring usable capacity solely from the existence of a connection." }, { "name": "Permitted interactions", "kind": "relation", "unit_or_values": "Allowed interface-to-interface actions with conditions and governing authority", "why_it_matters": "Separates physical connectivity from permission to use or alter it." } ], "affordances": [ "Identify which incident elements connect at the junction.", "Trace a proposed passage or transfer through its interfaces.", "Check whether a crossing constitutes a connection or remains separated.", "Assess whether a connection is usable under recorded conditions and limits.", "Determine prerequisites and authority for traversing, isolating, switching, or modifying the junction where applicable." ], "agent_conduct": { "may": [ "Record the routes, directions or modes connected at a junction and their operating state.", "Report damage, blockage or faults at a junction to its operator." ], "must_not": [ "Switch, close or modify a junction it is not authorized to operate.", "Disregard traffic controls, access restrictions or the priority of other users.", "Report a junction as usable when its condition or limits are unknown.", "Leave a junction cover or barrier open where people can be hurt." ], "requires_human": [ "Closing a junction or changing traffic routing in ways that affect other users." ] }, "ethics": { "considerations": [ "Junctions are where conflicts and failures concentrate, putting users and workers at risk.", "Closing a junction can cut off access to essential destinations and services." ], "affected_parties": [ "Affected parties include travellers across the connected transport modes and pedestrians.", "Affected parties include workers maintaining transport networks.", "Affected parties include communities relying on access through the junction." ] }, "owners": { "steward": "The owner or operator of the network the junction belongs to.", "master_systems": [ "Network asset registers of the operator" ] }, "visual_identification": [ "Connected roads, tracks, paths or waterways may provide visible opportunities to merge, turn or change routes.", "Signs, signals, markings or transfer facilities may identify permitted movements and connections.", "A visible crossing alone does not establish that traffic can transfer between its routes." ], "failure_modes_and_hazards": [ "Collisions can occur where traffic routes cross or merge.", "Conflicting movements or misunderstood controls can endanger travellers and workers.", "Blockage or closure can interrupt access and delay emergency services.", "Inaccessible or unclear transfer arrangements can exclude travellers or expose them to danger." ], "standards_and_regulation": [ "Vienna Convention on Road Signs and Signals, United Nations, for signing road junctions.", "IEC 60364 Low-voltage electrical installations, International Electrotechnical Commission." ], "what_it_is_for": [ "A transport junction occurs where roads, railway lines or other travel routes meet and permit movement between connected routes.", "It supports route selection, turning, merging or transfers between transport modes where suitable facilities exist.", "Navigation and transport planning use junction information to describe connectivity, permitted movements and traffic control." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q1777515: junction", "url": "https://www.wikidata.org/wiki/Q1777515", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Junction (traffic)", "url": "https://en.wikipedia.org/wiki/Junction_%28traffic%29", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "junction-identity-and-extent", "name": "Junction identity and extent", "description": "Establish the intended physical sense of junction and delimit its connection region.", "rationale": "The name is ambiguous, and the chosen boundary determines which interfaces and connections belong to the model.", "layers": [ { "id": "physical-sense", "name": "Physical sense", "description": "Identify what meeting or connection makes this thing a junction.", "findings": [ { "id": "qualifying-connection", "name": "Qualifying connection", "description": "Record the domain-specific criterion by which the meeting elements constitute a junction.", "questions": [ { "text": "What physical connection does 'junction' denote in the registry's originating record?", "kind": "definition", "id": "qualifying-connection-q01" }, { "text": "What evidence distinguishes this connection from mere proximity or an unconnected crossing?", "kind": "boundary", "id": "qualifying-connection-q02" } ] } ] }, { "id": "connection-region", "name": "Connection region", "description": "Locate the junction's limits relative to incident elements and neighbouring junctions.", "findings": [ { "id": "junction-boundary", "name": "Junction boundary", "description": "Record an explicit boundary convention for the physical meeting region.", "questions": [ { "text": "Where does each incident element end for the purposes of this model and the junction region begin?", "kind": "boundary", "id": "junction-boundary-q01" }, { "text": "Does the evidence describe one compound junction or several separately identifiable junctions?", "kind": "boundary", "id": "junction-boundary-q02" } ] } ] } ] }, { "id": "interfaces-and-topology", "name": "Interfaces and topology", "description": "Represent the elements entering the junction and the connections established among them.", "rationale": "A junction's defining information is its local connectivity, including connections that do not exist despite apparent intersection.", "layers": [ { "id": "incident-interfaces", "name": "Incident interfaces", "description": "Identify each attachment, entry, exit, or terminal under the relevant domain convention.", "findings": [ { "id": "interface-inventory", "name": "Interface inventory", "description": "Record incident elements with stable local interface identifiers and a stated counting basis.", "questions": [ { "text": "Which physical elements meet here, and through which identifiable interfaces?", "kind": "definition", "id": "interface-inventory-q01" }, { "text": "How many interfaces are present when counted by the chosen convention, such as road arms, pipe openings, or electrical terminals?", "kind": "measurement", "id": "interface-inventory-q02" } ] } ] }, { "id": "connection-map", "name": "Connection map", "description": "Describe direct connections, separations, and directional relationships between interfaces.", "findings": [ { "id": "pairwise-connectivity", "name": "Pairwise connectivity", "description": "Represent which interface pairs or groups are connected without assuming universal connectivity.", "questions": [ { "text": "Which interfaces connect directly, and which remain separated within the junction region?", "kind": "definition", "id": "pairwise-connectivity-q01" }, { "text": "Which connections are directional or depend on a selectable configuration?", "kind": "definition", "id": "pairwise-connectivity-q02" } ] } ] } ] }, { "id": "coupling-and-transfer", "name": "Coupling and transfer", "description": "Describe what the junction transmits or accommodates and the physical conditions required.", "rationale": "Topology alone cannot establish whether the junction supports the intended movement, conduction, flow, or force transmission.", "layers": [ { "id": "connection-mechanism", "name": "Connection mechanism", "description": "Identify how continuity or attachment is physically established.", "findings": [ { "id": "coupling-basis", "name": "Coupling basis", "description": "Record the applicable connection mechanism and the interface properties it requires.", "questions": [ { "text": "What passes through or is transmitted across this junction, or what attachment does it establish?", "kind": "definition", "id": "coupling-basis-q01" }, { "text": "Which geometric, material, or contact properties are necessary for the incident interfaces to connect as intended?", "kind": "measurement", "id": "coupling-basis-q02" } ] } ] }, { "id": "transfer-envelope", "name": "Transfer envelope", "description": "Record domain-specific limits on usable connection performance.", "findings": [ { "id": "junction-limits", "name": "Junction limits", "description": "Associate each verified limit with its connection, conditions, and evidence.", "questions": [ { "text": "Which measurable limits constrain use here, such as clearance, current, pressure, or transmitted load, and in what units?", "kind": "measurement", "id": "junction-limits-q01" }, { "text": "Which drawing, test, specification, or observation supports each limit and its applicability to this junction?", "kind": "provenance", "id": "junction-limits-q02" } ] } ] } ] }, { "id": "connection-state-and-intervention", "name": "Connection state and intervention", "description": "Assess current connection availability and the conditions for using or changing it.", "rationale": "A physically connected junction may be obstructed, degraded, restricted, or unsafe to alter without affecting incident elements.", "layers": [ { "id": "connection-condition", "name": "Connection condition", "description": "Record evidence of continuity, interruption, and deterioration at individual connections.", "findings": [ { "id": "usable-connection-state", "name": "Usable connection state", "description": "Distinguish observed physical condition from assumed availability.", "questions": [ { "text": "Which connections are currently established, interrupted, restricted, or unverified, and when was that state observed?", "kind": "measurement", "id": "usable-connection-state-q01" }, { "text": "Which observed defects or obstructions affect passage, conduction, sealing, or load transfer in the applicable domain?", "kind": "measurement", "id": "usable-connection-state-q02" } ] } ] }, { "id": "junction-actions", "name": "Junction actions", "description": "Relate proposed use or modification to permissions, configuration, and effects on connected elements.", "findings": [ { "id": "action-prerequisites", "name": "Action prerequisites", "description": "Record what must be established before an agent uses, isolates, switches, disconnects, or modifies a connection.", "questions": [ { "text": "Which proposed interactions are permitted, by whose authority, and under which connection states?", "kind": "action", "id": "action-prerequisites-q01" }, { "text": "Before changing this junction, which incident elements require isolation, support, diversion, or other domain-specific preparation?", "kind": "action", "id": "action-prerequisites-q02" }, { "text": "What verification is required before an altered connection can return to use?", "kind": "action", "id": "action-prerequisites-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": [ "No sense is recorded, and PHY.OBJ does not distinguish transport, piping, electrical, semiconductor, or structural meanings.", "The listed kinds represent distinct established uses of the word, not a confirmed taxonomy for this registry entry.", "Identifiers, applicable standards, and meaningful measurement ranges require the intended sense to be resolved; all statements here are recall-based." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of junction 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": [ "Road junction", "Railway junction", "Pipe junction", "Electrical conductor junction", "Semiconductor junction", "Structural junction" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of junction 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": [ "Connecting transport routes so traffic can change direction or route.", "Combining or dividing fluid flow in piping networks.", "Connecting electrical conductors into circuits.", "Providing interfaces between semiconductor regions that control electrical behaviour.", "Connecting structural elements to transfer loads." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of junction 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": [ "Transport junctions can create conflicting movements and collision hazards.", "Pipe junctions can leak, obstruct flow, or concentrate mechanical stress.", "Electrical conductor junctions can develop excessive resistance, overheating, or arcing.", "Semiconductor junctions can suffer electrical breakdown or thermal damage.", "Structural junctions can fail through fatigue, connection failure, or excessive deformation." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of junction 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": [ "In road terminology, British English commonly uses 'junction'; American English commonly uses 'intersection' for an at-grade crossing and 'interchange' for a grade-separated connection." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of junction 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": "joint", "difference": "A joint emphasizes the connection between adjoining parts; a junction can also be a branching or meeting region without a discrete joining component." }, { "name": "connector", "difference": "A connector is a component designed to establish a connection; a junction is the resulting meeting point or region and need not be a separate component." }, { "name": "crossing", "difference": "Routes can cross geometrically without connecting; a route junction provides a connection between them." }, { "name": "junction box", "difference": "A junction box is an enclosure that houses electrical connections, rather than the connections themselves." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of junction this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the originating registry record intend a road or railway junction, an electrical or semiconductor junction, a mechanical connection, or another physical sense?", "Does an existing Vercy world model already own the intended concept, requiring this registry entry to link to it?", "For the intended sense, can a two-element connection qualify, and what distinguishes a junction from a joint, connector, crossing, or intersection?", "What authoritative convention determines the boundary of one junction and the counting of its interfaces?", "Which domain-specific sources establish applicable operating limits, condition criteria, and intervention requirements?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 14, "questions": 23 } }