{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-11T04:06:21Z", "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": 1, "engine": "claude", "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-05T14:00:00Z", "ingestedAt": "2026-10-05T13:11:18+00:00", "fields": [ "agent_conduct", "ethics", "owners" ] }, "revisions": [ { "at": "2026-10-06T22:34:21+00:00", "engine": "codex", "fields": [ "agent_conduct", "definition", "distinguishing_features", "ethics", "failure_modes_and_hazards", "owners", "purpose", "visual_identification" ], "answering_review": "283d0b53691995ff442e1f32916676a05e00e4cc61d86035a7eaebf06595bd7a" } ], "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:26+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q1423035", "registryId": "vr.tr.tap-q1423035", "name": "tap", "version": "0.2.0-wave.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "ACT.ACT" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q1423035/", "model": { "registry_id": "vr.tr.tap-q1423035", "name": "tap", "purpose": "Let an agent describe and identify basketball shot-blocking actions, distinguish attempted blocks from successful blocks, and explain their relationship to fouls and goaltending under the applicable rules.", "definition": "A defensive action in basketball in which a player places a hand in the path of an opponent's shot toward the basket to obstruct or block the ball.", "what_it_is_for": "Producing a signal without force: getting attention, testing a surface, entering input, or marking time.", "affordances": [ "do it, with a finger, a tool or a machine", "detect it, which is how touchscreens and knock sensors work", "interpret it, where a pattern carries a meaning agreed in advance", "mistake incidental contact for it, which is the main failure" ], "distinguishing_features": [ "The action occurs when a defender challenges an opponent's shot toward the basket.", "The defender's hand obstructs or attempts to obstruct the ball's path.", "An attempted block does not necessarily make contact with the ball.", "Legality depends on the applicable basketball rules and the circumstances of the play." ], "appearance": "Not seen so much as heard and felt: a brief contact repeated, too short to be a push and too light to be a blow.", "visual_identification": [ "An opponent is shooting the ball toward the basket.", "A defender extends a hand into the shot's path.", "Contact with the ball may visibly alter its path.", "A single image may not establish contact, timing or the legality of the action." ], "physical_properties": [ { "quantity": "contact duration", "typical_range": "20-200", "unit": "ms", "note": "above roughly 500 ms most interfaces treat it as a hold" }, { "quantity": "interval for a double tap", "typical_range": "150-500", "unit": "ms", "note": "the window is a design choice and an accessibility issue" }, { "quantity": "force", "typical_range": "0.1-5", "unit": "N", "note": "above this it is a knock or a strike" } ], "families_and_kinds": [ "by purpose: attention, input, testing, rhythm, signalling", "by agent: finger, tool, machine", "by pattern: single, double, long sequence such as a coded knock" ], "related_models": [ { "relation": "is a kind of", "target": "physical action", "why": "inherits actor, target and outcome structure" }, { "relation": "is confused with", "target": "press", "why": "the difference is duration, which interfaces must decide by threshold" }, { "relation": "produces", "target": "input event", "why": "in a device the tap becomes an event with a timestamp and coordinates" }, { "relation": "is confused with", "target": "tap as a water fitting", "why": "a homonym in English; the fitting is a device and this is an act" } ], "identifiers": [], "standards_and_regulation": [ "Accessibility guidance on timing, which requires adjustable double-tap intervals", "Human interface guidelines from platform vendors, which define the gesture vocabulary" ], "failure_modes_and_hazards": [ "Contact during a block attempt can cause a foul or player injury.", "An apparent block can constitute goaltending or basket interference under the applicable rules.", "An obstructed view can lead to an incorrect judgement about ball contact or a foul.", "Confusing this sense with light tapping misrepresents the basketball action." ], "in_scope": [], "out_of_scope": [], "characteristics": [], "agent_conduct": { "may": [ "Describe shot-blocking actions in basketball footage it is authorized to analyse.", "Explain the distinction between a block attempt, a successful block and a possible rules violation.", "Flag uncertainty when the available view does not establish what happened." ], "must_not": [ "Encourage dangerous contact or deliberate injury during a block attempt.", "Present an uncertain judgement about a foul or goaltending as established fact.", "Treat every defensive hand movement near a shot as a successful block." ], "requires_human": [ "Making binding officiating decisions without explicitly delegated authority.", "Assessing a player's injury or fitness to continue playing." ] }, "ethics": { "considerations": [ "Player safety takes priority over preventing a basket.", "Analysis should apply rules consistently and acknowledge uncertainty.", "Commentary should distinguish a disputed play from an unsupported judgement about a player's intent." ], "affected_parties": [ "Players can be affected by physical contact and officiating decisions.", "Coaches and teams rely on accurate descriptions of defensive play.", "Officials are responsible for applying the rules within their authority." ] }, "owners": { "steward": "Nobody owns the action; the relevant basketball governing body maintains the applicable rules.", "master_systems": [] } }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q1423035: tap", "url": "https://www.wikidata.org/wiki/Q1423035", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Block (basketball)", "url": "https://en.wikipedia.org/wiki/Block_%28basketball%29", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "act-and-target", "name": "The act and its target", "description": "What is tapped, by what, and how.", "rationale": "A tap is defined by its target as much as by the motion: the same motion on a screen, a pipe and a shoulder are three different acts.", "layers": [ { "id": "actor-and-instrument", "name": "Actor and instrument", "description": "Who or what taps, and with what.", "findings": [ { "id": "actor-and-instrument-finding", "name": "Actor and instrument", "description": "The agent performing it and the thing used.", "questions": [ { "text": "Who or what performs this tap, and with what instrument?", "kind": "definition" }, { "text": "What changes about the act when the instrument changes?", "kind": "boundary" } ] } ] }, { "id": "target", "name": "Target and surface", "description": "What is tapped and how it responds.", "findings": [ { "id": "target-finding", "name": "Target and response", "description": "The surface struck and what it does in reply.", "questions": [ { "text": "What is being tapped, and what response does the surface give?", "kind": "definition" }, { "text": "What surfaces would not register it, and why?", "kind": "boundary" } ] } ] } ] }, { "id": "pattern-and-meaning", "name": "Pattern and meaning", "description": "What the tapping is meant to convey.", "rationale": "A tap carries meaning only against an agreed pattern, and the agreement is external to the act.", "layers": [ { "id": "pattern", "name": "Pattern and timing", "description": "Count, interval and rhythm.", "findings": [ { "id": "pattern-finding", "name": "Pattern definition", "description": "The pattern performed and the tolerances around it.", "questions": [ { "text": "What pattern of taps is performed, with what intervals?", "kind": "measurement" }, { "text": "What tolerance is allowed before the pattern is a different one?", "kind": "boundary" } ] } ] }, { "id": "meaning", "name": "Agreed meaning", "description": "The convention that gives it sense.", "findings": [ { "id": "meaning-finding", "name": "Convention in force", "description": "The code or convention that interprets it.", "questions": [ { "text": "Under what convention does this pattern carry meaning, and agreed by whom?", "kind": "provenance" }, { "text": "What should a receiver do with a pattern that matches no convention?", "kind": "action" } ] } ] } ] }, { "id": "detection-and-interpretation", "name": "Detection and interpretation", "description": "How a system decides a tap happened.", "rationale": "For a machine, a tap is a threshold decision, and every threshold excludes somebody.", "layers": [ { "id": "detection", "name": "Detection thresholds", "description": "Duration, force and area thresholds.", "findings": [ { "id": "detection-finding", "name": "Thresholds applied", "description": "The values that decide whether contact counts.", "questions": [ { "text": "What thresholds decide that a tap occurred in this system?", "kind": "measurement" }, { "text": "Who is excluded by those thresholds, and how is that mitigated?", "kind": "action" } ] } ] }, { "id": "disambiguation", "name": "Disambiguation", "description": "Telling it from press, hold and accidental contact.", "findings": [ { "id": "disambiguation-finding", "name": "Disambiguation rules", "description": "How competing interpretations are resolved.", "questions": [ { "text": "How does the system distinguish a tap from a press, a hold or incidental contact?", "kind": "definition" }, { "text": "What happens when the classification is wrong, and how is that recoverable?", "kind": "action" } ] } ] } ] }, { "id": "use-and-consequence", "name": "Use and consequence", "description": "What follows from it.", "rationale": "The consequence of a tap ranges from nothing to an irreversible action, and the model must say which.", "layers": [ { "id": "effect", "name": "Effect", "description": "What the tap causes.", "findings": [ { "id": "effect-finding", "name": "Caused effect", "description": "The action triggered and its reversibility.", "questions": [ { "text": "What does this tap cause, and is that reversible?", "kind": "action" }, { "text": "Which effects should require more than a tap, and why?", "kind": "boundary" } ] } ] }, { "id": "record", "name": "Record of the event", "description": "What is logged and what it proves.", "findings": [ { "id": "record-finding", "name": "Event record", "description": "What is recorded about the tap and its evidential value.", "questions": [ { "text": "What is recorded when this tap happens, with what timestamp and context?", "kind": "provenance" }, { "text": "What may not be inferred from that record about who performed it?", "kind": "boundary" } ] } ] } ] } ] }, "openQuestions": [ "Should the physical act and the interface event be separate models, given that one has force and the other has coordinates?", "How should intent be represented when it cannot be observed, only inferred?", "What thresholds should the model carry so that accessibility requirements are visible rather than buried in an implementation?" ], "statistics": { "bundles": 4, "layers": 8, "findings": 8, "questions": 16 } }