{ "model": { "rank": 2591, "code": "thing-q160464", "model_id": "vr.tr.button", "name": "button", "purpose": "Enable an AI agent to recognise a physical button, assess its attachment and functional state, and decide whether and how it may be fastened, pressed, released, repaired or replaced.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q160464/", "tier": 2, "score": 101, "payload": { "layer": "wikidata", "aliases": [ "covered button", "lapel button", "squatchee", "Bachelor button", "toggle", "pin-back button", "shirt stud", "collar button", "campaign button" ], "aliasCount": 9, "merged": 9, "knownIn": 101, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": "vr.tr.button-2", "source": { "dataset": "wikidata", "item": "Q160464", "url": "https://www.wikidata.org/wiki/Q160464", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T10:13:32Z", "providers": [ "Codex", "Grok" ], "missingProviders": [], "pass": 2, "cost": { "grok": { "usd": 0.04757676, "turns": 3, "seconds": 161.3, "error": null }, "codex": { "seconds": 71.4, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\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: 01a07b59-67c9-7fc2-a071-ba1136c6040b\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: button\nRegistry id: vr.tr.button\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\nA Vercy mod" } } }, "metaModel": { "id": "THING-Q160464", "registryId": "vr.tr.button", "name": "button", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q160464/", "model": { "registry_id": "vr.tr.button", "name": "button", "purpose": "Enable an AI agent to recognise a physical button, assess its attachment and functional state, and decide whether and how it may be fastened, pressed, released, repaired or replaced.", "definition": "A knot, disc, or similar rigid object that, when forced through a buttonhole or loop, fastens one part of a garment or other flexible substrate to another, or that is attached to such a substrate purely as ornament.", "scope_statement": "This model owns the physical button as a discrete fastening element or press-operated control, including its working interfaces and observable states; both senses remain provisionally included because the registry records no definition.", "in_scope": [ "Physical buttons used to fasten garments, textiles or other flexible assemblies", "Physical buttons used to initiate a control input through pressing", "Button geometry, material, markings and accessible contact surfaces", "Attachment to a host and compatibility with a fastening counterpart or control mechanism", "Engagement, movement, damage and evidence supporting permitted actions" ], "out_of_scope": [ "Graphical buttons and other software interface elements", "The complete garment, enclosure or appliance hosting the button", "The complete electrical switch, circuit or controlled system behind a button", "Buttonholes, loops and other fastening counterparts as independently maintained objects", "Zippers, hooks, buckles and other fasteners whose operation does not use a button", "Decorative badges or ornaments without a fastening or press-control role" ], "distinguishing_features": [ "A fastening button retains a counterpart such as a hole or loop by passing through it and resisting unintended withdrawal; a bead or ornament without that role does not pass this test.", "A control button presents a discrete surface intended for pressing; a control operated principally by rotation or sliding is better identified as a knob or slider.", "A physical button has a tangible component or bounded physical contact surface; a rendered clickable image alone is a graphical button.", "A button may be only the user-contact component of a switch assembly; identify whether the observed object includes the switching mechanism before treating the two as equivalent.", "For press studs and other mating fasteners, inspect the engagement mechanism rather than relying on the name 'button'; their inclusion requires a registry boundary decision." ], "characteristics": [ { "name": "Functional role", "kind": "category", "unit_or_values": "fastening; press control; combined; unresolved", "why_it_matters": "Selects the relevant recognition tests, states and actions." }, { "name": "Working dimensions", "kind": "measurement", "unit_or_values": "mm for face width, thickness, projection and applicable attachment dimensions", "why_it_matters": "Supports counterpart fit, finger access and replacement assessment." }, { "name": "Material and surface", "kind": "category", "unit_or_values": "observed or documented material, coating and texture; unknown", "why_it_matters": "Helps assess grip, cracking, wear and appropriate cleaning or repair methods." }, { "name": "Attachment method", "kind": "category", "unit_or_values": "sew-through holes; shank; rivet; clip; threaded mount; integral mounting; other; unknown", "why_it_matters": "Determines how the button is retained and how it can be removed or replaced." }, { "name": "Host and working counterpart", "kind": "relation", "unit_or_values": "host object plus buttonhole, loop, actuator or other identified interface", "why_it_matters": "A button's usability depends on the specific assembly it serves." }, { "name": "Fastening engagement", "kind": "state", "unit_or_values": "disengaged; partly engaged; engaged; trapped; unknown; not applicable", "why_it_matters": "Distinguishes a secure closure from an incomplete or obstructed fastening." }, { "name": "Control position and return behaviour", "kind": "state", "unit_or_values": "resting; depressed; latched; stuck; unknown; not applicable, with observed return behaviour", "why_it_matters": "Separates normal movement from a retained or failed position." }, { "name": "Operating force and movement", "kind": "measurement", "unit_or_values": "N and mm, with direction, test conditions and applicable operating mode", "why_it_matters": "Supports assessment of operability without assuming that all buttons share a force or travel threshold." }, { "name": "Attachment and working-surface condition", "kind": "state", "unit_or_values": "observed looseness, cracks, missing material, wear, contamination or obstruction", "why_it_matters": "Identifies defects that can prevent operation or cause detachment." }, { "name": "Indicated and verified function", "kind": "relation", "unit_or_values": "marking or documentation linked to intended function, separately from observed outcome", "why_it_matters": "Prevents an agent from treating a label or successful press as proof of the resulting system action." } ], "affordances": [ "Inspect and identify the button's role, host, counterpart and markings.", "Fasten or unfasten a compatible button and counterpart when access and condition permit.", "Press and release a control button when its function and action authority are established.", "Check attachment, clearance and movement using an appropriate non-damaging method.", "Clean, reattach or replace the button using methods compatible with its material and host.", "Defer operation and record an unresolved function, incompatible fit or suspected defect." ] }, "sources": [ { "id": "astm-d2050-23", "title": "ASTM D2050-23, Standard Terminology Relating to Fasteners and Closures Used with Textiles", "url": "https://www.astm.org/d2050-23.html", "what_it_supports": "Industry definition of a button; distinction of sew-through flange versus sew-through shank; ligne as the trade size unit (1 ligne = 0.635 mm).", "url_status": "live" }, { "id": "wikipedia-button", "title": "Button", "url": "https://en.wikipedia.org/wiki/Button", "what_it_supports": "Attachment styles (flat/sew-through, shank, stud, toggle, covered, worked), ligne sizing, men's-right/women's-left convention, materials, and Qiaotou manufacturing share.", "url_status": "live" }, { "id": "wikidata-q160464", "title": "button (Q160464)", "url": "https://www.wikidata.org/wiki/Q160464", "what_it_supports": "Canonical identifier as a small clothing fastener; explicit difference from a push-button; BnF subject ID.", "url_status": "live" }, { "id": "britannica-button", "title": "Button (clothing accessory)", "url": "https://www.britannica.com/topic/button-clothing-accessory", "what_it_supports": "Specialist description of holes or shank sewn to one side and passed through a loop or hole; decorative as well as functional use; historical materials and plastic mass production.", "url_status": "blocked" }, { "id": "iso-11610-2023", "title": "ISO 11610:2023 Protective clothing - Vocabulary", "url": "https://www.iso.org/standard/76610.html", "what_it_supports": "Places the button among garment closures, listed separately from slide fastener, press fastener (snap), touch-and-close fastener, and toggle button.", "url_status": "blocked" }, { "id": "wikipedia-knopf", "title": "Knopf", "url": "https://de.wikipedia.org/wiki/Knopf", "what_it_supports": "German trade kinds: Ösenknopf (shank), Lochknopf (sew-through), Nietenknopf (jeans/rivet).", "url_status": "live" }, { "id": "cpsc-toy-safety", "title": "Toy Safety Business Guidance", "url": "https://www.cpsc.gov/Business--Manufacturing/Business-Education/Toy-Safety", "what_it_supports": "ASTM F963 made mandatory by 16 CFR part 1250; small-parts regime at 16 CFR part 1501.", "url_status": "live" }, { "id": "nra-childrens-apparel", "title": "Children's Apparel Product Safety Guidelines", "url": "https://www.nationalretail.org.au/resource/childrens-apparel-product-safety-guidelines/", "what_it_supports": "Detachment, breakage, sharp edges, and chemical hazards of buttons; 70 N for 10 s attachment test under AS/NZS ISO 8124.1.", "url_status": "live" }, { "id": "gs1-us-closure-codes", "title": "GS1 US Best Practice Guideline for Exchanging Product Images and Attributes", "url": "https://www.gs1us.org/", "what_it_supports": "Retail closure code GM03CLOSBN for Button, distinct from Snap (GM03CLOSSN) and Toggle (GM03CLOSTO).", "url_status": "live" } ], "structure": { "bundles": [ { "id": "button-role-and-recognition", "name": "Button role and recognition", "description": "Establishes which physical button role is present and what component is being modelled.", "rationale": "The word button can identify a fastening element or a control surface, which require different state judgements and actions.", "layers": [ { "id": "functional-identification", "name": "Functional identification", "description": "Identifies the button through its intended interaction.", "findings": [ { "id": "button-role", "name": "Button role", "description": "Record evidence for fastening, press-control or combined use without inferring function from appearance alone.", "questions": [ { "text": "Does this component retain a fastening counterpart, accept a press input, or perform both roles?", "kind": "definition", "id": "button-role-q01" }, { "text": "What observation, host documentation or other evidence establishes that role?", "kind": "provenance", "id": "button-role-q02" } ] } ] }, { "id": "component-boundary", "name": "Component boundary", "description": "Separates the button from its host, counterpart and associated mechanism.", "findings": [ { "id": "modelled-button-extent", "name": "Modelled button extent", "description": "Record whether the identified thing is a fastening body, a removable control cap or a larger integrated component.", "questions": [ { "text": "Where does this button end and its mounting, counterpart or switch mechanism begin?", "kind": "boundary", "id": "modelled-button-extent-q01" }, { "text": "What observable feature distinguishes it from an ornament, knob, slider or mating snap fastener?", "kind": "definition", "id": "modelled-button-extent-q02" } ] } ] } ] }, { "id": "button-fit-and-retention", "name": "Button fit and retention", "description": "Describes the geometry and attachment that let the button work in its particular assembly.", "rationale": "A recognisable button can still be unusable because it does not fit its counterpart or is inadequately attached.", "layers": [ { "id": "working-geometry", "name": "Working geometry", "description": "Captures dimensions at the interfaces used for fastening or pressing.", "findings": [ { "id": "counterpart-and-access-fit", "name": "Counterpart and access fit", "description": "Record fit to a hole or loop for fastening, or clearance and contact access for a control button.", "questions": [ { "text": "Which face, thickness, shank or clearance dimensions determine whether this button works with its identified counterpart?", "kind": "measurement", "id": "counterpart-and-access-fit-q01" }, { "text": "Can it pass through and retain the fastening counterpart, or move through its intended press path, without interference?", "kind": "measurement", "id": "counterpart-and-access-fit-q02" } ] } ] }, { "id": "host-attachment", "name": "Host attachment", "description": "Identifies how the button is held to its host.", "findings": [ { "id": "attachment-security", "name": "Attachment security", "description": "Record the retention method and evidence of looseness or separation at that interface.", "questions": [ { "text": "Is the button retained by thread through holes, a shank, a rivet, a clip or another identifiable mounting?", "kind": "definition", "id": "attachment-security-q01" }, { "text": "What observed movement, thread damage or mounting defect indicates that retention needs attention?", "kind": "measurement", "id": "attachment-security-q02" } ] } ] } ] }, { "id": "button-engagement-and-response", "name": "Button engagement and response", "description": "Records role-specific operating states and separates physical operation from its intended result.", "rationale": "A fastened appearance may conceal partial engagement, and a depressed control does not prove that its command took effect.", "layers": [ { "id": "fastening-state", "name": "Fastening state", "description": "Assesses how a fastening button engages its counterpart; not applicable to control-only buttons.", "findings": [ { "id": "closure-engagement", "name": "Closure engagement", "description": "Record whether the counterpart is fully retained and whether tension or distortion compromises the closure.", "questions": [ { "text": "Has the button passed fully through the intended hole or loop, leaving the counterpart retained behind its working face?", "kind": "measurement", "id": "closure-engagement-q01" }, { "text": "Can the closure be released through its intended motion without forcing the button, attachment or counterpart?", "kind": "action", "id": "closure-engagement-q02" } ] } ] }, { "id": "press-response", "name": "Press response", "description": "Assesses control-button movement and feedback; not applicable to fastening-only buttons.", "findings": [ { "id": "actuation-and-return", "name": "Actuation and return", "description": "Record press movement, tactile or other feedback, return or latching behaviour, and separately verified downstream response.", "questions": [ { "text": "What force, travel and release behaviour are observed, and what evidence establishes the expected behaviour for this button?", "kind": "measurement", "id": "actuation-and-return-q01" }, { "text": "What evidence independently confirms whether pressing this button produced the intended action?", "kind": "provenance", "id": "actuation-and-return-q02" } ] } ] } ] }, { "id": "button-condition-and-intervention", "name": "Button condition and intervention", "description": "Connects button-specific defects and function evidence to operation, maintenance and replacement decisions.", "rationale": "The agent needs to distinguish a usable button from one requiring repair and establish the consequences before operating a control.", "layers": [ { "id": "functional-damage", "name": "Functional damage", "description": "Assesses damage at the button face, attachment features and movement interfaces.", "findings": [ { "id": "defects-affecting-use", "name": "Defects affecting use", "description": "Record cracks through sewing holes or shanks, broken retaining edges, loose caps and obstructions to pressing.", "questions": [ { "text": "Are there cracks, worn retaining edges, loose attachment features or contaminants that interfere with this button's specific function?", "kind": "measurement", "id": "defects-affecting-use-q01" }, { "text": "Does the observed defect permit continued use, require restricted use or justify taking the button out of service, according to available evidence?", "kind": "action", "id": "defects-affecting-use-q02" } ] } ] }, { "id": "operation-and-replacement-decisions", "name": "Operation and replacement decisions", "description": "Establishes prerequisites for pressing, servicing or substituting the button.", "findings": [ { "id": "justified-button-action", "name": "Justified button action", "description": "Record the known function, authority and compatibility evidence needed for the proposed operation or intervention.", "questions": [ { "text": "Before pressing this control, what establishes its function, the relevant system state and the agent's authority to trigger that action?", "kind": "action", "id": "justified-button-action-q01" }, { "text": "For reattachment or replacement, which dimensions, mounting details, material properties and markings must match the host's requirements?", "kind": "boundary", "id": "justified-button-action-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-kinds", "name": "Kinds and varieties", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "sew-through flange (two-hole and four-hole)", "shank, including self-shank", "tack, jeans, or rivet button (mechanically clinched, not sewn)", "fabric-covered", "worked or cloth (Dorset, death-head, crocheted, or knotted frog/Mandarin)", "assembled or composite (joined dissimilar materials)", "stud (removable shirt stud or cuff-style push-through)", "magnetic" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of button this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "scheme": "Wikidata", "value_or_pattern": "Q160464", "note": "Item 'button': small fastener used in clothing." }, { "scheme": "BnF", "value_or_pattern": "119693859", "note": "Subject named as Boutons." }, { "scheme": "GS1 US closure code", "value_or_pattern": "GM03CLOSBN", "note": "Product-attribute code for a button closure, distinct from snap and toggle codes." }, { "scheme": "ASTM ligne (button size)", "value_or_pattern": "integer L where 1 ligne = 0.635 mm (0.025 in); 40 L = 1 in", "note": "Trade diameter of apparel buttons, not a unique instance identifier." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of button this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "ASTM D2050-23 Terminology Relating to Fasteners and Closures Used with Textiles (ASTM International) - button terms apply to sew-through flange and shank buttons.", "ISO 11610:2023 Protective clothing - Vocabulary (ISO) - button listed as a garment closure, separate from press fastener and toggle button.", "ASTM D7842 holding strength of tack and prong attached button fasteners (ASTM International).", "EN 71-1 Safety of toys - Mechanical and physical properties, clause 8.4 tension test (CEN), applied in apparel specs to trims that fit the small-parts cylinder: typically 90 N for more than 10 s.", "ASTM F963 Standard Consumer Safety Specification for Toy Safety, mandatory in the United States via 16 CFR part 1250 (ASTM International / U.S. CPSC); 90 N tension is widely reused for children's garment trims.", "16 CFR part 1501 Small Parts Regulation (U.S. CPSC) - children's clothing buttons are listed among articles exempt from the federal small-parts ban, though industry still pull-tests them.", "AS/NZS ISO 8124.1 torque and tension tests (Standards Australia / Standards New Zealand) - children's apparel guidance uses a 70 N, 10 s attachment minimum." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of button this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Sewn or clinched onto shirts, jackets, coats, trousers, bags, wallets, and bedding to close overlapping edges through a buttonhole or loop.", "Shirt fronts and cuffs typically use small sew-through buttons (about 16 ligne / 10 mm); suit jackets about 32 ligne / 20 mm; coats 36-40 ligne and larger, often shanked so they sit above thick cloth.", "Metal tack or jeans buttons clinch the waistband of denim and workwear without sewing thread.", "Rows of buttons on cuffs, double-breasted fronts, and livery coats are often ornamental rather than working closures.", "Most of the world's supply is mass-moulded plastic, metal, shell, or wood; Qiaotou in Yongjia County, China, is reported as the dominant manufacturing centre.", "Collected as studio craft, archaeological finds, uniform insignia, and (historically in the United States) stamped clothing buttons used in political campaigns." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of button this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "quantity": "diameter (ligne)", "typical_range": "16 L (shirts) to 32 L (jackets) to 40 L and above (coats); about 10-25+ mm", "unit": "ligne (1 L = 0.635 mm) or millimetre" }, { "quantity": "attachment holding force (children's apparel practice)", "typical_range": "70 N for 10 s (AS/NZS ISO 8124.1 guidance) to 90 N for 10 s (EN 71-1 / ASTM F963-derived buyer specs)", "unit": "newton" }, { "quantity": "sew-through hole count", "typical_range": "2 or 4", "unit": "count" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of button this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Thread or clinch failure so the button detaches; a detached button that fits the small-parts cylinder is a choking, aspiration, or ingestion hazard for young children.", "Chainstitch attachment unravels from a single broken stitch; lockstitch (ISO 4915 type 301) is specified in workwear practice to avoid that.", "Assembled or multi-component buttons separate into pieces; brittle natural materials (shell, bone, horn, wood) crack or shatter, leaving sharp edges.", "Pull-through or tearing of lightweight or knitted fabric when the button is stronger than the substrate; children's guidance requires attachment through two layers or a fusible backing.", "Coatings and alloys can carry restricted substances or nickel that irritate skin; food-like shapes invite mouthing.", "Spare buttons sewn onto children's garments become extra small parts; workwear practice also treats a loose button as foreign-object debris around machinery." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of button this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Classic Western clothing places the button on the wearer's right for men and left for women; many Hasidic and some other Jewish men reverse this and button right over left.", "German trade names distinguish Ösenknopf (shank), Lochknopf (sew-through holes), and Nietenknopf (jeans/rivet); English 'press stud' (UK) versus 'snap' (US) names the related fastener, not the sewn button.", "ISO protective-clothing vocabulary lists 'toggle button' separately from 'button'; GS1 retail codes likewise split Button, Snap, and Toggle.", "Late-17th-century French law required silk-covered buttons to protect the silk trades; England at the same period restricted fabric buttons to protect the button-makers' guild.", "Stamped clothing and later pin-back campaign buttons are a mainly United States political practice; manufacturing volume is concentrated in Qiaotou, China." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of button this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "name": "snap fastener (press stud, press button, dome, popper)", "difference": "Two interlocking discs that engage by pressure; they do not pass through a buttonhole. ASTM D2050 and ISO 11610 treat snaps as a separate fastener class from buttons." }, { "name": "push-button", "difference": "A control surface that actuates a switch or mechanism rather than joining fabric; Wikidata marks Q160464 as different from the push-button item." }, { "name": "toggle (toggle button)", "difference": "A short bar passed endways through a loop or frog and then rotated; ISO 11610 lists toggle button as its own closure example, not as a disc-through-buttonhole button." }, { "name": "slide fastener (zip)", "difference": "A continuous linear closure of interlocking elements, not a single-point disc or knot through an opening." }, { "name": "rivet", "difference": "A permanent clinch not meant to be opened; a jeans button looks similar but is a working fastener paired with a buttonhole." }, { "name": "pin-back badge (campaign button)", "difference": "Pinned on as a display, not sewn through a buttonhole to close a garment; modern campaign 'buttons' are badges, unlike the earlier stamped clothing buttons." }, { "name": "hook-and-loop (touch-and-close) fastener", "difference": "A surface fastener of hooks engaging loops, listed separately from buttons in ASTM D2050 and ISO 11610." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of button this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does vr.tr.button intentionally include both fastening buttons and physical control buttons, or does another registry entry own one of these senses?", "Are press studs, toggle fasteners and decorative non-functional buttons included here or assigned to neighbouring registered things?", "Does the registry treat a control button as its contact surface or cap, or as the complete push-button switch assembly?", "Which documented tolerances, operating forces and retention criteria apply to each intended host and use context?", "How should fixed touch-sensitive physical controls be distinguished from moving push buttons and graphical buttons?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 16, "questions": 24 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "device, machine or tool", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a button, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a physical button, assess its attachment and functional state, and decide whether and how it may be fastened, pressed, released, repaired or replaced.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: covered button, lapel button, squatchee, Bachelor button, toggle, pin-back button, shirt stud, collar button, campaign button.", "9 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 101 Wikipedia languages, which is a measure of how widely the thing is known, not of how important it is." ], "openQuestionsForResearch": [ "Which of the bundles below does a real task actually need, and which are ceremony?", "What does this thing have that the facets do not capture at all?", "Which neighbouring kind is most often confused with a button, and on what evidence are they told apart?" ], "whatItIsMadeOf": "matter you can touch", "physicalCharacter": [ "Mobility varies between examples.", "Does nothing on its own; everything it does, something else did to it.", "These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing." ], "whatCanBeDoneWithIt": [ "observe it, measure it, record its state" ], "howItIsRecognised": [ "Recognised by form, by the arrangement of its controls, and by markings - a plate, a model number, a certification mark. Form alone rarely separates two models that do very different things." ], "relatedModels": [ { "relation": "covers", "note": "Finer kinds folded into this entry because telling them apart needs a task that asks for it. Each is a model waiting to be split out when one does.", "targets": [ "covered button", "lapel button", "squatchee", "Bachelor button", "toggle", "pin-back button", "shirt stud", "collar button", "campaign button" ] } ], "standing": "Described in 101 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 9 finer distinctions are held inside this entry as names rather than as separate models.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one button from another, and a button from things that resemble it.", "rationale": "Recognition comes before every other claim. Without stable identity nothing else in the model can be trusted to be about the same thing twice.", "layers": [ { "id": "naming-and-identifiers", "name": "Names and identifiers", "description": "The names this thing goes by and the identifiers that survive translation and time.", "findings": [ { "id": "preferred-name-and-aliases", "name": "Preferred name, aliases and local names", "description": "Which name to use, which names mean the same thing, and which merely sound similar.", "questions": [ { "id": "preferred-name-and-aliases-q01", "text": "What identifies and describes the name of a button, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "preferred-name-and-aliases-q02", "text": "Who or what asserted this about the name of a button, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "preferred-name-and-aliases-q03", "text": "What may an agent decide or do once the name of a button is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "stable-identifiers", "name": "Stable identifiers and external keys", "description": "Identifiers that keep pointing at this kind of thing across systems and languages.", "questions": [ { "id": "stable-identifiers-q01", "text": "What identifies and describes an identifier for a button, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stable-identifiers-q02", "text": "Who or what asserted this about an identifier for a button, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stable-identifiers-q03", "text": "What may an agent decide or do once an identifier for a button is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "classification-and-granularity", "name": "Classification and granularity", "description": "Where a button sits among kinds, and how finely a task needs to cut it.", "findings": [ { "id": "kind-and-parents", "name": "Kind, parents and neighbouring kinds", "description": "The classes this thing belongs to and the ones it is next to.", "questions": [ { "id": "kind-and-parents-q01", "text": "What identifies and describes the kind of a button, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "kind-and-parents-q02", "text": "Who or what asserted this about the kind of a button, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "kind-and-parents-q03", "text": "What may an agent decide or do once the kind of a button is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "distinguishing-features", "name": "Distinguishing features", "description": "What separates a button from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a button, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "distinguishing-features-q02", "text": "Who or what asserted this about what distinguishes a button, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "distinguishing-features-q03", "text": "What may an agent decide or do once what distinguishes a button is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "form-and-composition", "name": "Form, composition and condition", "description": "What a button is made of, what shape and size it takes, and what state it is in.", "rationale": "A physical thing can be measured, and a model that cannot record its measurements cannot support any decision that depends on them.", "layers": [ { "id": "form-and-dimensions", "name": "Form and dimensions", "description": "Shape, size, mass and the ranges these take across examples.", "findings": [ { "id": "measurable-dimensions", "name": "Measurable dimensions and their units", "description": "The quantities worth recording and the units they are recorded in.", "questions": [ { "id": "measurable-dimensions-q01", "text": "What identifies and describes the dimensions of a button, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "measurable-dimensions-q02", "text": "Who or what asserted this about the dimensions of a button, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "measurable-dimensions-q03", "text": "What may an agent decide or do once the dimensions of a button is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "material-and-composition", "name": "Material and composition", "description": "Materials, parts and how they are put together.", "findings": [ { "id": "parts-and-materials", "name": "Parts and materials", "description": "What a button is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a button, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "parts-and-materials-q02", "text": "Who or what asserted this about the composition of a button, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "parts-and-materials-q03", "text": "What may an agent decide or do once the composition of a button is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "condition-and-integrity", "name": "Condition and integrity", "description": "Wear, damage, health and the difference between working and broken.", "findings": [ { "id": "condition-assessment", "name": "Condition, damage and health", "description": "How the condition of a button is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a button, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "condition-assessment-q02", "text": "Who or what asserted this about the condition of a button, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "condition-assessment-q03", "text": "What may an agent decide or do once the condition of a button is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "place-and-movement", "name": "Place and movement", "description": "Where a button is, how it got there and where it may go (varies).", "rationale": "A thing that can move needs its position recorded with a time, or every later claim about it is about a place it has left.", "layers": [ { "id": "location-and-placement", "name": "Location and placement", "description": "Position, containment and the reference frame the position is given in.", "findings": [ { "id": "position-and-frame", "name": "Position, container and reference frame", "description": "Where a button is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a button, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "position-and-frame-q02", "text": "Who or what asserted this about the location of a button, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "position-and-frame-q03", "text": "What may an agent decide or do once the location of a button is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "movement-and-transfer", "name": "Movement and transfer", "description": "How a button is carried, installed or relocated.", "findings": [ { "id": "movement-events", "name": "Movement events and constraints", "description": "What counts as a movement, what records it and what limits it.", "questions": [ { "id": "movement-events-q01", "text": "What identifies and describes the movement of a button, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "movement-events-q02", "text": "Who or what asserted this about the movement of a button, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "movement-events-q03", "text": "What may an agent decide or do once the movement of a button is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "state-and-lifecycle", "name": "State and lifecycle", "description": "The states a button passes through and the events that move it between them.", "rationale": "Most decisions about a thing depend on what state it is in now, which is a claim with a time on it, not a property.", "layers": [ { "id": "lifecycle-stages", "name": "Lifecycle stages", "description": "From coming into existence to ceasing to be one of these.", "findings": [ { "id": "stages-and-transitions", "name": "Stages and transitions", "description": "The stages worth naming and what moves a button between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a button, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stages-and-transitions-q02", "text": "Who or what asserted this about the lifecycle of a button, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stages-and-transitions-q03", "text": "What may an agent decide or do once the lifecycle of a button is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "observations-and-status", "name": "Observations and current status", "description": "What is observed about a button, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a button is recorded so that it can be superseded rather than overwritten.", "questions": [ { "id": "observation-record-q01", "text": "What identifies and describes an observation of a button, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "observation-record-q02", "text": "Who or what asserted this about an observation of a button, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "observation-record-q03", "text": "What may an agent decide or do once an observation of a button is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "function-and-principle", "name": "Function and operating principle", "description": "What button is for and how it achieves it.", "rationale": "Two devices with the same name can work on different principles, and the principle is what predicts failure and constrains use.", "layers": [ { "id": "intended-function", "name": "Intended function", "description": "The job it does, and the jobs it is used for anyway.", "findings": [ { "id": "function-record", "name": "Function, principle and variants", "description": "What it does, how, and which variants do it differently.", "questions": [ { "id": "function-record-q01", "text": "What function does button perform, on what operating principle, and which variants differ in that principle?", "kind": "definition" }, { "id": "function-record-q02", "text": "What use falls outside the intended function but happens in practice?", "kind": "boundary" } ] } ] }, { "id": "capacity-and-rating", "name": "Capacity and rating", "description": "The numbers that say what it can do and where it stops.", "findings": [ { "id": "ratings", "name": "Ratings and their conditions", "description": "Rated capacity, power, throughput and the conditions each assumes.", "questions": [ { "id": "ratings-q01", "text": "What ratings characterise button, in what units, and under what stated conditions?", "kind": "measurement" }, { "id": "ratings-q02", "text": "What happens beyond the rating - degradation, refusal, damage - and how is that detected?", "kind": "action" } ] } ] } ] }, { "id": "operation-and-state", "name": "Operation, controls and state", "description": "How button is operated and what state it is in right now.", "rationale": "An agent acting on a device needs its current state and the controls that change it, not just its specification.", "layers": [ { "id": "controls-and-modes", "name": "Controls and modes", "description": "What can be set, what that changes, and what is interlocked.", "findings": [ { "id": "control-surface", "name": "Control surface and interlocks", "description": "The settings available and the conditions that block them.", "questions": [ { "id": "control-surface-q01", "text": "What controls and modes does button have, and what does each change?", "kind": "definition" }, { "id": "control-surface-q02", "text": "Which actions are interlocked or forbidden in which state, and what must be true before acting?", "kind": "action" } ] } ] }, { "id": "condition-and-maintenance", "name": "Condition and maintenance", "description": "Wear, service intervals, consumables and the line between working and broken.", "findings": [ { "id": "service-record", "name": "Condition, service and consumables", "description": "What is consumed, what is serviced, and how condition is judged.", "questions": [ { "id": "service-record-q01", "text": "What consumables and service does button need, at what interval, and on whose authority?", "kind": "measurement" }, { "id": "service-record-q02", "text": "What evidence separates a unit that is working from one that is out of service?", "kind": "boundary" } ] } ] } ] }, { "id": "kind-model-unit", "name": "Kind, model and unit", "description": "Whether a claim about button is about the kind, a product line, or one physical unit.", "rationale": "This is the boundary most often got wrong for made things, and getting it wrong mixes a catalogue entry with the machine in the yard.", "layers": [ { "id": "level-of-reference", "name": "Level of reference", "description": "The three levels and what belongs at each.", "findings": [ { "id": "level-rules", "name": "What belongs to kind, model and unit", "description": "Which properties are shared by all of them and which are not.", "questions": [ { "id": "level-rules-q01", "text": "Which facts about button hold for every one of them, which for a model, and which only for one unit?", "kind": "boundary" }, { "id": "level-rules-q02", "text": "What identifies an individual unit, and what should an agent do when it has only the kind?", "kind": "action" } ] } ] }, { "id": "standards-and-conformity", "name": "Standards and conformity", "description": "The standards a working example must meet and who attests it.", "findings": [ { "id": "conformity", "name": "Standards, marks and attestation", "description": "Which standard applies, who certifies, and what the mark means.", "questions": [ { "id": "conformity-q01", "text": "Which standards govern button, issued by whom, and what does conformity actually assert?", "kind": "provenance" }, { "id": "conformity-q02", "text": "What may an agent conclude from a certification mark, and what may it not?", "kind": "boundary" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a button came from and when it held.", "rationale": "A claim without a source and a time cannot be superseded, only overwritten, and an agent that overwrites loses the ability to explain itself.", "layers": [ { "id": "source-and-authority", "name": "Source and authority", "description": "Who said it, on what evidence, and how strongly.", "findings": [ { "id": "claim-provenance", "name": "Claim provenance and confidence", "description": "The authority behind each claim about a button and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a button, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "claim-provenance-q02", "text": "Who or what asserted this about a claim about a button, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "claim-provenance-q03", "text": "What may an agent decide or do once a claim about a button is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "time-and-versions", "name": "Time, versions and supersession", "description": "When a claim was true, when it was learnt, and what replaced it.", "findings": [ { "id": "validity-and-supersession", "name": "Validity period and supersession", "description": "How an old claim about a button is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a button, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "validity-and-supersession-q02", "text": "Who or what asserted this about the validity of a claim about a button, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "validity-and-supersession-q03", "text": "What may an agent decide or do once the validity of a claim about a button is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 8, "layers": 17, "findings": 19, "questions": 51 } } } }