{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T10:29:57Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 19.1, "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: 01a09529-8719-7fb2-b5f4-faac702ccee7\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: inferior vesical artery\nSense to describe: (none recorded)\nDomain code: PHY.LIV\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 0", "usd": 0.0, "recall": true }, "codex": { "seconds": 76.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: 01a09529-8719-7ad3-8c64-b77a10a02458\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: inferior vesical artery\nRegistry id: vr.tr.inferior-vesical-artery\nPlane / domain: PHY / PHY.LIV\nRegistry definition: (none recorded)\nNames folded in" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:45:39+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:32+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q707686", "registryId": "vr.tr.inferior-vesical-artery", "name": "inferior vesical artery", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.LIV" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q707686/", "model": { "registry_id": "vr.tr.inferior-vesical-artery", "name": "inferior vesical artery", "purpose": "Enable an agent to identify an inferior vesical artery, record its individual anatomy and perfusion state, and support review of actions that could affect lower urinary bladder blood supply.", "definition": "The inferior vesical artery is a variable pelvic artery, typically described in males as a branch of the anterior division of the internal iliac artery, that supplies the lower urinary bladder and commonly contributes branches to the prostate and seminal vesicle.", "scope_statement": "This draft models the inferior vesical artery registered as vr.tr.inferior-vesical-artery in PHY / PHY.LIV as an anatomical vessel type and its individual occurrences, owning vessel identification, origin, course, branches, supplied territories, observed condition and intervention dependencies.", "in_scope": [ "Identification of a particular inferior vesical artery by side, continuity and supplied territory", "Parent artery, shared trunks, course and terminal branching", "Observed contribution to blood supply of the bladder base and neck", "Anatomical variation and boundaries with neighbouring pelvic arteries", "Vessel condition, evidence quality and consequences of proposed vessel manipulation" ], "out_of_scope": [ "Whole-organ bladder structure, storage function and urinary disorders", "The complete internal iliac arterial tree", "Independent models of the superior vesical, vaginal, prostatic and middle rectal arteries", "Whole-person diagnosis, treatment selection and procedural technique", "Organism taxonomy, conservation status and population demography" ], "distinguishing_features": [ "Trace an arterial lumen toward the bladder base or neck; pelvic location alone does not establish inferior vesical identity.", "Distinguish it from a superior vesical artery using the combined origin, course and distribution rather than the word 'vesical' or one branch point.", "Distinguish a vesical vessel with prostatic branches from a separately identified prostatic artery by documenting where their paths diverge and which territories each reaches.", "Separate it from an accompanying vein by demonstrating arterial continuity or arterial-phase filling rather than proximity to the bladder.", "Do not use sex alone to exclude its presence: female occurrences and variable origins have been documented in an [anatomical study](https://pubmed.ncbi.nlm.nih.gov/28229186/)." ], "characteristics": [ { "name": "Identification status", "kind": "state", "unit_or_values": "confirmed; probable; indeterminate; not visualized; absence demonstrated", "why_it_matters": "Prevents an unobserved small vessel from being recorded as anatomically absent." }, { "name": "Laterality and multiplicity", "kind": "category", "unit_or_values": "left; right; indeterminate; number of separately traced vessels per side", "why_it_matters": "Keeps individual vessel occurrences distinct and avoids assuming bilateral symmetry." }, { "name": "Parent vessel and shared trunk", "kind": "relation", "unit_or_values": "identified parent artery, branch point and any common-trunk partners; unresolved", "why_it_matters": "Origin alone may not identify the vessel, but its topology determines what proximal manipulation could affect." }, { "name": "Bladder supply territory", "kind": "relation", "unit_or_values": "observed bladder regions supplied, with evidence and confidence", "why_it_matters": "Connects the vessel name to the lower bladder territory that motivates its identification." }, { "name": "Extra-vesical branch destinations", "kind": "relation", "unit_or_values": "observed destination structures for each branch; absent; unresolved", "why_it_matters": "Records shared supply without assuming every occurrence has the same reproductive or urinary branches." }, { "name": "Luminal diameter", "kind": "measurement", "unit_or_values": "mm at a specified segment, acquisition method and time", "why_it_matters": "Supports interpretation of visibility, narrowing and procedural accessibility." }, { "name": "Patency and vessel integrity", "kind": "state", "unit_or_values": "patent; narrowed; occluded; disrupted; previously ligated or embolized; indeterminate", "why_it_matters": "Distinguishes anatomical existence from current ability to convey blood." }, { "name": "Collateral connections", "kind": "relation", "unit_or_values": "identified communicating vessels, observed flow direction and assessment conditions", "why_it_matters": "A visible connection does not by itself establish adequate alternative perfusion." } ], "affordances": [ "Annotate a candidate inferior vesical artery on imaging or a dissection record with its side and identification confidence.", "Trace its parent vessel, common trunks and terminal branches to distinguish it from adjacent pelvic arteries.", "Compare serial observations of caliber, patency and lower bladder perfusion.", "Flag branches and shared territories potentially affected by planned ligation, embolization or pelvic dissection.", "Request targeted anatomical or imaging review when vessel identity, absence or collateral adequacy remains unresolved." ], "agent_conduct": { "may": [ "Explain the anatomy of the inferior vesical artery and its variations in general terms.", "Support surgeons or students with reference anatomy on request." ], "must_not": [ "Interpret a person's imaging as a diagnosis.", "Recommend embolisation or surgery for a specific person.", "Disclose a person's urological records without consent.", "Present one textbook pattern as certain for every patient when the artery varies." ], "requires_human": [ "Treatment decisions such as prostate artery embolisation." ] }, "ethics": { "considerations": [ "Anatomical variation matters for surgical safety; oversimplified information can mislead.", "Urological conditions are private and deserve dignity." ], "affected_parties": [ "Patients undergoing pelvic or prostate procedures", "Students", "Surgeons" ] }, "owners": { "steward": "Nobody owns it; it is part of each person's body.", "master_systems": [] }, "visual_identification": [ "A small artery arising deep in the pelvis and running to the base of the bladder and prostate." ], "failure_modes_and_hazards": [ "Bleeding after prostate or bladder surgery can come from its branches.", "Variable origin makes it easy to misidentify during procedures." ], "what_it_is_for": [ "The inferior vesical artery contributes to blood supply of the lower urinary bladder and, in typical male anatomy, adjacent reproductive structures.", "Its variable origin and branches are relevant to pelvic imaging and planning of urological or vascular interventions." ], "standards_and_regulation": [ "Terminologia Anatomica, maintained by the Federative International Programme for Anatomical Terminology of the International Federation of Associations of Anatomists, provides standardized anatomical nomenclature for the inferior vesical artery." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q707686: inferior vesical artery", "url": "https://www.wikidata.org/wiki/Q707686", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Inferior vesical artery", "url": "https://en.wikipedia.org/wiki/Inferior_vesical_artery", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "vesical-vessel-identity", "name": "Vesical vessel identity", "description": "Establish which observed arterial structure the registered name denotes.", "rationale": "Small pelvic branches can be misnamed when identification relies on location, sex or one apparent origin.", "layers": [ { "id": "territorial-identification", "name": "Territorial identification", "description": "Connect the candidate vessel to a documented bladder destination.", "findings": [ { "id": "inferior-bladder-continuity", "name": "Inferior bladder continuity", "description": "Record the evidence connecting an arterial lumen to the bladder base or neck; anatomical dissection describes inferior vesical supply to the bladder base in an [original anatomical report](https://pmc.ncbi.nlm.nih.gov/articles/PMC6022419/).", "questions": [ { "text": "What continuous arterial path reaches the bladder base or neck in this occurrence?", "kind": "definition", "id": "inferior-bladder-continuity-q01" }, { "text": "Which observed features distinguish this path from a superior vesical branch or nearby vein?", "kind": "boundary", "id": "inferior-bladder-continuity-q02" } ] } ] }, { "id": "occurrence-and-naming", "name": "Occurrence and naming", "description": "Separate the anatomical type from a particular sided vessel and its recorded label.", "findings": [ { "id": "sided-vessel-assignment", "name": "Sided vessel assignment", "description": "Attach the name to a specific subject or specimen, side and traced vessel rather than to an assumed bilateral pattern.", "questions": [ { "text": "Which subject or specimen, side and separately traced vessel does this identification concern?", "kind": "provenance", "id": "sided-vessel-assignment-q01" }, { "text": "Does the recorded name denote the entire artery, a common trunk or only a terminal vesical branch?", "kind": "boundary", "id": "sided-vessel-assignment-q02" } ] } ] } ] }, { "id": "pelvic-origin-and-course", "name": "Pelvic origin and course", "description": "Describe the artery's position within the pelvic branching network.", "rationale": "A useful model must represent the observed route and shared origins instead of imposing a single textbook configuration.", "layers": [ { "id": "parent-and-common-trunks", "name": "Parent and common trunks", "description": "Identify the immediate parent and vessels sharing its proximal route.", "findings": [ { "id": "observed-branch-topology", "name": "Observed branch topology", "description": "Record the immediate parent, proximal continuity and common-trunk partners without treating a proposed origin as observed.", "questions": [ { "text": "From which artery does the identified inferior vesical vessel arise, and how was that junction demonstrated?", "kind": "provenance", "id": "observed-branch-topology-q01" }, { "text": "Which other arterial territories share its trunk before the vesical branch separates?", "kind": "boundary", "id": "observed-branch-topology-q02" } ] } ] }, { "id": "course-and-landmarks", "name": "Course and landmarks", "description": "Locate the vessel relative to structures encountered around the lower bladder.", "findings": [ { "id": "local-pelvic-route", "name": "Local pelvic route", "description": "Document the actual route toward the bladder and its relationships to the distal ureter, bladder wall and adjacent operative landmarks.", "questions": [ { "text": "What landmarks locate the artery from its origin to its entry into the bladder supply territory?", "kind": "measurement", "id": "local-pelvic-route-q01" }, { "text": "Which relationships to the distal ureter or adjacent pelvic structures are directly observed rather than inferred?", "kind": "provenance", "id": "local-pelvic-route-q02" } ] } ] } ] }, { "id": "supply-and-collateral-dependence", "name": "Supply and collateral dependence", "description": "Connect the artery and its branches to demonstrated tissue perfusion.", "rationale": "The consequences of changing this vessel depend on its actual destinations and alternative supply.", "layers": [ { "id": "terminal-supply-map", "name": "Terminal supply map", "description": "Separate lower bladder supply from any additional branch destinations.", "findings": [ { "id": "vesical-and-extra-vesical-territories", "name": "Vesical and extra-vesical territories", "description": "Record bladder regions and any additional supplied structures branch by branch, keeping anatomical proximity separate from demonstrated supply.", "questions": [ { "text": "Which portions of the bladder base, trigone or neck receive demonstrated supply from this vessel?", "kind": "measurement", "id": "vesical-and-extra-vesical-territories-q01" }, { "text": "Are branches to the prostate, seminal vesicle, distal ureter or other structures demonstrated, and where do they separate?", "kind": "boundary", "id": "vesical-and-extra-vesical-territories-q02" } ] } ] }, { "id": "alternative-perfusion", "name": "Alternative perfusion", "description": "Represent communicating vessels and the limits of collateral evidence.", "findings": [ { "id": "collateral-pathway-evidence", "name": "Collateral pathway evidence", "description": "Distinguish an anatomical anastomosis from evidence that another vessel can maintain perfusion of the affected bladder territory.", "questions": [ { "text": "Which connections to other vesical or pelvic arteries are demonstrated, and under what observation conditions?", "kind": "provenance", "id": "collateral-pathway-evidence-q01" }, { "text": "What evidence supports adequate alternative perfusion if this artery's flow is reduced or interrupted?", "kind": "action", "id": "collateral-pathway-evidence-q02" } ] } ] } ] }, { "id": "variation-and-observation-limits", "name": "Variation and observation limits", "description": "Represent variable anatomy and limits on detecting or naming the artery.", "rationale": "Neither sex-based conventions nor failure to visualize the vessel reliably settles an individual occurrence.", "layers": [ { "id": "sex-and-anatomical-configuration", "name": "Sex and anatomical configuration", "description": "Record relevant pelvic organs and naming conventions without forcing a fixed sex-based vessel pattern.", "findings": [ { "id": "vaginal-artery-boundary", "name": "Vaginal artery boundary", "description": "Preserve the distinction between inferior vesical and vaginal vessels while documenting how a source names their relationship; variable female occurrences were reported in an [anatomical study](https://pubmed.ncbi.nlm.nih.gov/28229186/).", "questions": [ { "text": "What pelvic organ configuration and vessel branching are actually documented in this individual?", "kind": "provenance", "id": "vaginal-artery-boundary-q01" }, { "text": "Does the source distinguish an inferior vesical artery from a vaginal artery or describe a vesical branch under another name?", "kind": "boundary", "id": "vaginal-artery-boundary-q02" } ] } ] }, { "id": "detectability-and-confidence", "name": "Detectability and confidence", "description": "Explain what the observation method can establish about this small pelvic vessel.", "findings": [ { "id": "nonvisualization-versus-absence", "name": "Nonvisualization versus absence", "description": "Record acquisition or dissection limitations before interpreting a missing vessel as absent.", "questions": [ { "text": "What method, resolution, contrast timing or dissection extent supports the identification?", "kind": "provenance", "id": "nonvisualization-versus-absence-q01" }, { "text": "If the artery is not seen, what evidence distinguishes true absence from inadequate visualization, occlusion or prior interruption?", "kind": "boundary", "id": "nonvisualization-versus-absence-q02" } ] } ] } ] }, { "id": "vessel-state-and-action-dependencies", "name": "Vessel state and action dependencies", "description": "Assess the observed vessel condition and anatomical dependencies relevant to a proposed action.", "rationale": "An artery may be identifiable yet unable to convey blood, and manipulation may affect territories beyond the intended target.", "layers": [ { "id": "lumen-and-integrity", "name": "Lumen and integrity", "description": "Record segment-specific caliber, patency and evidence of injury or previous intervention.", "findings": [ { "id": "current-vessel-condition", "name": "Current vessel condition", "description": "Localize observed narrowing, occlusion, disruption or treatment material to the identified artery and observation time.", "questions": [ { "text": "What are the measured luminal diameter and patency at each clinically relevant segment?", "kind": "measurement", "id": "current-vessel-condition-q01" }, { "text": "What evidence identifies bleeding, structural injury or prior ligation or embolization involving this vessel?", "kind": "provenance", "id": "current-vessel-condition-q02" } ] } ] }, { "id": "intervention-territory-review", "name": "Intervention territory review", "description": "Connect a proposed manipulation to the specific branches and perfusion territories it could affect.", "findings": [ { "id": "affected-branches-and-review-needs", "name": "Affected branches and review needs", "description": "Support anatomical review of a proposed action by identifying its location, downstream dependencies and unresolved collateral supply.", "questions": [ { "text": "Which bladder and extra-vesical territories lie downstream of the proposed ligation, embolization or dissection site?", "kind": "action", "id": "affected-branches-and-review-needs-q01" }, { "text": "Which unresolved vessel identities, shared trunks or collateral pathways require specialist review before the proposed action?", "kind": "action", "id": "affected-branches-and-review-needs-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": [ "Origin, branching pattern, and supplied territory vary; the conventional description does not establish an individual's anatomy.", "Descriptions of a distinct inferior vesical artery in females vary among anatomical sources.", "No vessel dimensions, numerical ontology identifiers, or population frequencies are asserted from recall." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of inferior vesical artery 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": "Terminologia Anatomica", "value_or_pattern": "arteria vesicalis inferior", "note": "Standard Latin anatomical name; no numerical identifier asserted." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of inferior vesical artery 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": [ "Terminologia Anatomica, maintained by the Federative International Programme for Anatomical Terminology (FIPAT), standardizes anatomical nomenclature." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of inferior vesical artery 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": [ "Anatomical landmark in pelvic surgery and interpretation of pelvic angiography.", "Relevant to identifying arterial supply during prostate artery embolization.", "Relevant to preserving bladder perfusion and controlling bleeding during pelvic procedures." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of inferior vesical artery 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": [ "Injury during pelvic surgery or trauma can cause hemorrhage.", "Variable origins and shared arterial branches can complicate selective catheterization.", "Unintended embolization of vesical branches can cause bladder ischemic injury." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of inferior vesical artery 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": "Superior vesical arteries", "difference": "Usually arise from the patent portion of the umbilical artery and predominantly supply the upper bladder." }, { "name": "Vaginal artery", "difference": "Supplies the vagina and commonly supplies the lower bladder in females, assuming territory attributed to the inferior vesical artery in standard male descriptions." }, { "name": "Internal iliac artery", "difference": "A larger parent vessel supplying multiple pelvic territories; the inferior vesical artery is one of its variable visceral branches." }, { "name": "Prostatic arteries", "difference": "Defined by their supply to the prostate; they may arise from the inferior vesical artery or other pelvic arteries." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of inferior vesical artery this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which authoritative anatomical terminology and identifiers should anchor this entry, particularly for female inferior vesical vessels and vaginal artery branches?", "What minimum combination of origin, course and supplied territory reliably distinguishes an inferior vesical artery from a prostatic artery or another vesical branch?", "How do reported frequencies of presence, multiplicity and origin vary with population, pelvic anatomy, dissection method and imaging method?", "Which measurement protocols and reference data are adequate for comparing caliber and recognizing abnormal narrowing in this small vessel?", "What evidence can establish sufficient collateral perfusion of the bladder base and neck after interruption of a particular inferior vesical artery?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 16, "questions": 26 } }