{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T06:07:38Z", "providers": [ "Claude" ], "breadth": "written by Claude from model knowledge without web access - no source was read, every claim is a lead to verify", "pass": 2, "wave": 2, "engine": "claude", "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-05T23:50:00Z", "ingestedAt": "2026-10-05T20:57:34+00:00", "fields": [ "agent_conduct", "ethics", "owners" ] }, "revisions": [ { "at": "2026-10-06T22:45:38+00:00", "engine": "codex", "fields": [ "agent_conduct", "definition", "distinguishing_features", "ethics", "failure_modes_and_hazards", "owners", "purpose", "visual_identification" ], "answering_review": "9a8088e0a395097196f799dd07dac4f0b835ba6ca389e60ccd698d5a83015ad7" } ], "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:29+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q2443617", "registryId": "vr.tr.port-q2443617", "name": "port", "version": "0.2.0-wave.2", "entryKind": "thing", "family": "Thing Registry", "domain": [ "XCT.REL" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q2443617/", "model": { "registry_id": "vr.tr.port-q2443617", "name": "port", "purpose": "Let an agent explain circuit ports, their terminal voltages and currents, and their role in describing connections between electrical networks.", "definition": "In circuit theory, a pair of terminals through which an electrical network or circuit connects to an external circuit, with current entering one terminal equal to current leaving the other and a voltage defined between the terminals.", "what_it_is_for": "Connection points for devices and programs.", "affordances": [ "explain hardware, network and software ports", "describe standards", "support troubleshooting generally", "separate other senses" ], "distinguishing_features": [ "Each port consists of a pair of terminals.", "The current entering one terminal equals the current leaving the other.", "Port voltage is defined between the two terminals.", "A network may be represented using one or more ports." ], "appearance": "Sockets on devices; numbers in network configuration.", "visual_identification": [ "A circuit diagram may show a port as a pair of terminals at a network boundary.", "Voltage polarity marks and current arrows may identify the port's reference conventions.", "A physical socket or numbered network service does not by itself identify a circuit-theory port." ], "physical_properties": [], "families_and_kinds": [ "physical hardware ports", "network ports and port numbers", "software and application ports", "serial and legacy ports", "virtual and console ports" ], "related_models": [ { "relation": "is a kind of", "target": "connection", "why": "category" }, { "relation": "is related to", "target": "computer architecture", "why": "input and output in system design" }, { "relation": "is related to", "target": "internet service provider", "why": "network services reached by ports" }, { "relation": "is related to", "target": "cyberattack", "why": "ports as points of exposure" } ], "identifiers": [], "standards_and_regulation": [ "Hardware interface standards", "Registered port number assignments", "Security guidance on open ports" ], "failure_modes_and_hazards": [ "Treating arbitrary terminals as a port without the equal-current condition can invalidate a model.", "Inconsistent voltage polarities and current directions can produce incorrect results.", "Confusing circuit ports with computing interfaces can lead to inappropriate assumptions.", "Physical circuit connections can expose people and equipment to electrical hazards." ], "in_scope": [], "out_of_scope": [], "characteristics": [], "agent_conduct": { "may": [ "Explain circuit ports and the equal-current condition.", "Interpret port voltage and current conventions in circuit models.", "Describe one-port and multiport network representations." ], "must_not": [ "Assume that any two terminals satisfy the port condition.", "Confuse circuit-theory ports with network service numbers or software interfaces.", "Treat an abstract port model as proof that a physical connection is safe.", "Authorize physical circuit changes beyond its assigned authority." ], "requires_human": [ "Safety-critical decisions about physical circuit connections require a qualified human." ] }, "ethics": { "considerations": [ "Incorrect circuit models can endanger people and damage equipment.", "Model assumptions and reference conventions should be explicit." ], "affected_parties": [ "People working with the circuit are affected.", "Equipment owners are affected.", "Users of connected equipment are affected." ] }, "owners": { "steward": "The responsible circuit designer or equipment owner oversees the applicable circuit model and physical implementation.", "master_systems": [] } }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q2443617: port", "url": "https://www.wikidata.org/wiki/Q2443617", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Port (circuit theory)", "url": "https://en.wikipedia.org/wiki/Port_%28circuit_theory%29", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "understand", "name": "Understand", "description": "What a port is.", "rationale": "Computing.", "layers": [ { "id": "concept", "name": "Concept", "description": "Concept and kinds.", "findings": [ { "id": "concept-finding", "name": "Concept", "description": "Concept.", "questions": [ { "text": "What is a port, and how do physical, network and software ports differ?", "kind": "definition" }, { "text": "Is the computing or another sense of port meant?", "kind": "boundary" } ] } ] }, { "id": "standards", "name": "Standards", "description": "Standards.", "findings": [ { "id": "standards-finding", "name": "Standards", "description": "Standards.", "questions": [ { "text": "What standards govern hardware ports, and how are network port numbers assigned?", "kind": "provenance" }, { "text": "Which entry fits a specific interface standard?", "kind": "action" } ] } ] } ] }, { "id": "use", "name": "Use", "description": "Configuration and troubleshooting.", "rationale": "Practice.", "layers": [ { "id": "configure", "name": "Configure", "description": "Configuring ports.", "findings": [ { "id": "configure-finding", "name": "Configure", "description": "Configuration.", "questions": [ { "text": "How are network ports configured, forwarded and checked for a service, in general terms?", "kind": "action" }, { "text": "Which entry fits network configuration?", "kind": "action" } ] } ] }, { "id": "troubleshoot", "name": "Troubleshoot", "description": "Troubleshooting.", "findings": [ { "id": "troubleshoot-finding", "name": "Troubleshoot", "description": "Troubleshooting.", "questions": [ { "text": "Why might a device or service not connect, and how are port problems diagnosed?", "kind": "action" }, { "text": "Which entry fits network troubleshooting?", "kind": "action" } ] } ] } ] }, { "id": "security", "name": "Security", "description": "Security.", "rationale": "Boundaries.", "layers": [ { "id": "exposure", "name": "Exposure", "description": "Open ports and exposure.", "findings": [ { "id": "exposure-finding", "name": "Exposure", "description": "Exposure.", "questions": [ { "text": "Why do open ports matter for security, and what defensive practices do security bodies recommend?", "kind": "provenance" }, { "text": "Is the request seeking operational attack detail, which must be declined?", "kind": "boundary" } ] } ] }, { "id": "firewalls", "name": "Firewalls", "description": "Firewalls.", "findings": [ { "id": "firewalls-finding", "name": "Firewalls", "description": "Firewalls.", "questions": [ { "text": "How do firewalls control traffic by port?", "kind": "provenance" }, { "text": "Which entry fits firewalls?", "kind": "action" } ] } ] } ] }, { "id": "learn", "name": "Learn", "description": "History and teaching.", "rationale": "Education.", "layers": [ { "id": "history", "name": "History", "description": "History.", "findings": [ { "id": "history-finding", "name": "History", "description": "History.", "questions": [ { "text": "How did hardware ports evolve from serial and parallel to universal serial bus, and how did network ports arise?", "kind": "provenance" }, { "text": "Which references are standard?", "kind": "provenance" } ] } ] }, { "id": "teach", "name": "Teach", "description": "Teaching.", "findings": [ { "id": "teach-finding", "name": "Teach", "description": "Teaching.", "questions": [ { "text": "How can ports be taught in computing education?", "kind": "action" }, { "text": "Which misconceptions arise?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Should network ports be a separate entry?", "How should interface standards be linked?", "How should security guidance be linked?" ], "statistics": { "bundles": 4, "layers": 8, "findings": 8, "questions": 16 } }