{ "model": { "rank": 3782, "code": "thing-q721587", "model_id": "vr.tr.telegraphy", "name": "telegraphy", "purpose": "Enable an agent to recognise a telegraphic communication practice, assess whether a message can be conveyed and interpreted reliably, and determine the next appropriate operating action.", "family": "Thing Registry", "category": "Activities and processes", "status": "research-draft", "kind": "thing", "plane": "ACT", "domain": "ACT.ACT", "industry": "", "version": "", "url": "/models/thing/q721587/", "tier": 2, "score": 82, "payload": { "layer": "wikidata", "aliases": [ "wireless telegraphy", "flag semaphore", "alphabetical telegraphy", "International Code of Signals", "High Speed Telegraphy" ], "aliasCount": 5, "merged": 5, "knownIn": 82, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q721587", "url": "https://www.wikidata.org/wiki/Q721587", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T15:08:36Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 30.6, "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: 01a07c68-ed34-7053-b8a8-914c561b8449\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: telegraphy\nSense to describe: (none recorded)\nDomain code: ACT.ACT\nAlso known as: (none)\n\n\nContext for this batch of 801 things:\n# Batch 004: 1001 regis", "usd": 0, "recall": true }, "codex": { "seconds": 70.9, "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: 01a07c68-ed59-77f1-84e9-c62369a3a369\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: telegraphy\nRegistry id: vr.tr.telegraphy\nPlane / domain: ACT / ACT.ACT\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nCo" } } }, "metaModel": { "id": "THING-Q721587", "registryId": "vr.tr.telegraphy", "name": "telegraphy", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "ACT.ACT" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q721587/", "model": { "registry_id": "vr.tr.telegraphy", "name": "telegraphy", "purpose": "Enable an agent to recognise a telegraphic communication practice, assess whether a message can be conveyed and interpreted reliably, and determine the next appropriate operating action.", "definition": "Telegraphy is the communication of messages over a distance by transmitting discrete coded signals that represent written characters or other agreed meanings, using optical, electrical, radio or other signalling means.", "scope_statement": "This model owns telegraphy as an activity of communicating messages over distance through agreed discrete signals, including optical, wired electrical and radiotelegraphic practices; it records the relationship between message, code, signalling procedure, channel and reception.", "in_scope": [ "The operational definition of telegraphy used in a particular setting", "Message preparation, encoding, signalling, reception and decoding", "Optical, wired electrical and radio signalling arrangements", "Station addressing, relaying, channel access and operator coordination", "Transmission quality, error handling and evidence of message delivery" ], "out_of_scope": [ "Detailed construction and maintenance of telegraph instruments", "General electromagnetic propagation and electrical circuit theory", "Telephony and the transmission of speech as speech", "General computer networking beyond its boundary with telegraphy", "The institutional history and commercial organisation of telegraph services", "The subject matter and truth of messages being transmitted" ], "distinguishing_features": [ "The activity conveys a message through an agreed repertoire of distinguishable signals; merely detecting a remote event is insufficient.", "Record whether message elements are represented by signal states, combinations or timing, rather than assuming that telegraphy means Morse code.", "Identify a signalling and interpretation procedure between separated endpoints; writing a code on paper alone is not a telegraphic exchange.", "Classify the bearer separately from the activity: optical apparatus, wires and radio can support telegraphy.", "For teleprinters, facsimile and digital data links, require an explicit inclusion rule because boundaries depend on the historical or technical definition adopted." ], "characteristics": [ { "name": "Operational definition", "kind": "category", "unit_or_values": "Named historical, technical or service-specific definition with explicit inclusion criteria", "why_it_matters": "Prevents an agent from silently treating one period's meaning of telegraphy as universal." }, { "name": "Signalling bearer", "kind": "category", "unit_or_values": "Optical; wired electrical; radio; other documented bearer", "why_it_matters": "Determines the relevant visibility, circuit or reception conditions." }, { "name": "Code and repertoire", "kind": "relation", "unit_or_values": "Reference to a code, version, character repertoire and procedural signals", "why_it_matters": "Determines what can be expressed and whether the receiving endpoint can interpret it." }, { "name": "Signal discrimination rule", "kind": "category", "unit_or_values": "Timing intervals; positions; electrical states; combinations; documented thresholds", "why_it_matters": "Makes explicit how meaningful signal elements are distinguished." }, { "name": "Operating mode", "kind": "category", "unit_or_values": "Manual, automatic or mixed; one-way or two-way; alternating or simultaneous transmission", "why_it_matters": "Determines who controls transmission and how competing signals are avoided." }, { "name": "Signalling rate", "kind": "measurement", "unit_or_values": "Symbols per second, baud where applicable, or words per minute with the reference-word convention stated", "why_it_matters": "Supports compatibility and capacity judgments without equating unlike rate measures." }, { "name": "Station and relay path", "kind": "relation", "unit_or_values": "Origin, destination, intermediate stations and addressing scheme", "why_it_matters": "Distinguishes a successful individual link from completed end-to-end communication." }, { "name": "Reception condition", "kind": "state", "unit_or_values": "Available; degraded; unavailable; unknown, with bearer-specific observations", "why_it_matters": "Supports decisions to transmit, reduce speed, repeat or wait." }, { "name": "Observed transcription error", "kind": "measurement", "unit_or_values": "Incorrect, missing or extra characters or groups per checked total, with comparison method", "why_it_matters": "Separates measured accuracy from a receiver's impression of readability." }, { "name": "Message progress", "kind": "state", "unit_or_values": "Prepared; queued; partly transmitted; transmitted; reception acknowledged; delivered; failed; unknown", "why_it_matters": "Prevents transmission, acknowledgement and delivery from being treated as equivalent." } ], "affordances": [ "Classify a communication practice against an explicit definition of telegraphy.", "Check whether endpoints share compatible codes, repertoires and operating procedures.", "Prepare and encode a message while recording substitutions and unsupported characters.", "Select a feasible signalling rate and relay path from observed operating conditions.", "Interpret received signals while preserving uncertain characters and requesting clarification where supported.", "Track transmission, repetition, acknowledgement and delivery as separate events." ] }, "sources": [], "structure": { "bundles": [ { "id": "telegraphic-identity", "name": "Telegraphic identity", "description": "Establishes which sense of telegraphy applies and what constitutes an instance.", "rationale": "The registry has no definition, and telegraphy must not be reduced to a single code or instrument.", "layers": [ { "id": "definition-and-boundary", "name": "Definition and boundary", "description": "Records the adopted meaning and its treatment of neighbouring communication activities.", "findings": [ { "id": "explicit-inclusion-rule", "name": "Explicit inclusion rule", "description": "Record the criteria used to include a practice as telegraphy, together with the authority and context of that definition.", "questions": [ { "text": "Which definition governs this instance, and what observable features satisfy it?", "kind": "definition", "id": "explicit-inclusion-rule-q01" }, { "text": "How does that definition treat teleprinters, facsimile and modern digital links?", "kind": "boundary", "id": "explicit-inclusion-rule-q02" } ] } ] }, { "id": "practice-and-apparatus", "name": "Practice and apparatus", "description": "Separates the communication activity from the devices and media supporting it.", "findings": [ { "id": "message-bearing-exchange", "name": "Message-bearing exchange", "description": "Identify the separated endpoints, intended message and agreed signalling practice rather than classifying an apparatus by its name alone.", "questions": [ { "text": "What message is conveyed between which endpoints through which agreed signals?", "kind": "definition", "id": "message-bearing-exchange-q01" }, { "text": "Is the observed activity message communication, remote measurement, remote control or a combination requiring separate models?", "kind": "boundary", "id": "message-bearing-exchange-q02" } ] } ] } ] }, { "id": "message-and-code", "name": "Message and code", "description": "Connects intended content to the symbols and procedures used to convey it.", "rationale": "Successful signalling does not ensure that the intended text is representable or interpreted correctly.", "layers": [ { "id": "repertoire-and-encoding", "name": "Repertoire and encoding", "description": "Records the code actually used and any changes imposed on the message.", "findings": [ { "id": "representable-message", "name": "Representable message", "description": "Retain the original message, encoded form and any transliteration, abbreviation or substitution needed by the selected repertoire.", "questions": [ { "text": "Which code and version are used, and where is their mapping documented?", "kind": "provenance", "id": "representable-message-q01" }, { "text": "Which message elements cannot be represented directly, and what substitutions are permitted?", "kind": "action", "id": "representable-message-q02" } ] } ] }, { "id": "framing-and-procedure", "name": "Framing and procedure", "description": "Distinguishes message content from signals that organise its transmission.", "findings": [ { "id": "message-boundaries", "name": "Message boundaries", "description": "Record how character, group and message boundaries are recognised and how procedural signals are distinguished from content.", "questions": [ { "text": "What marks character separation, message start and message completion in this system?", "kind": "definition", "id": "message-boundaries-q01" }, { "text": "How should the receiver interpret an ambiguous procedural signal or missing boundary?", "kind": "action", "id": "message-boundaries-q02" } ] } ] } ] }, { "id": "signal-and-channel", "name": "Signal and channel", "description": "Describes how encoded elements become observable signals under actual channel conditions.", "rationale": "Telegraphic readability depends on distinguishable states and timing, with different constraints for optical, wire and radio links.", "layers": [ { "id": "signal-realisation", "name": "Signal realisation", "description": "Records the physical distinctions through which the selected code is conveyed.", "findings": [ { "id": "discriminable-signal-elements", "name": "Discriminable signal elements", "description": "Specify the positions, states, durations or combinations the receiver must distinguish, including relevant spacing and tolerances.", "questions": [ { "text": "Which observable distinctions carry code elements on this link?", "kind": "definition", "id": "discriminable-signal-elements-q01" }, { "text": "What timing, spacing or state thresholds separate valid elements from ambiguous ones?", "kind": "measurement", "id": "discriminable-signal-elements-q02" } ] } ] }, { "id": "bearer-conditions", "name": "Bearer conditions", "description": "Assesses whether current conditions support the required signal distinctions.", "findings": [ { "id": "usable-link", "name": "Usable link", "description": "Record bearer-specific evidence such as optical visibility, circuit continuity or radio interference, and relate it to observed readability.", "questions": [ { "text": "Which observed channel conditions currently obscure, distort or interrupt the signals?", "kind": "measurement", "id": "usable-link-q01" }, { "text": "What evidence supports continuing, slowing transmission, changing the link or suspending operation?", "kind": "action", "id": "usable-link-q02" } ] } ] } ] }, { "id": "stations-and-traffic", "name": "Stations and traffic", "description": "Organises communication across endpoints, shared channels and relay stages.", "rationale": "A correctly encoded message can still reach the wrong station, collide with another transmission or stall at a relay.", "layers": [ { "id": "addressing-and-relay", "name": "Addressing and relay", "description": "Records station identity, intended destination and the handling of intermediate transmissions.", "findings": [ { "id": "traceable-message-path", "name": "Traceable message path", "description": "Identify each required hop and whether an intermediate station forwards signals directly or receives and retransmits a message.", "questions": [ { "text": "How are the intended receiving station and final addressee distinguished and addressed?", "kind": "definition", "id": "traceable-message-path-q01" }, { "text": "Which relay stages are required, and what evidence connects their received and forwarded messages?", "kind": "provenance", "id": "traceable-message-path-q02" } ] } ] }, { "id": "channel-access", "name": "Channel access", "description": "Records who may transmit, when transmission begins and how interruptions are handled.", "findings": [ { "id": "coordinated-transmission", "name": "Coordinated transmission", "description": "Specify the applicable calling, readiness, turn-taking and priority procedures, including whether the link permits simultaneous communication.", "questions": [ { "text": "What establishes that the destination is ready and the channel is available?", "kind": "definition", "id": "coordinated-transmission-q01" }, { "text": "What procedure applies when transmissions overlap or urgent traffic interrupts a message?", "kind": "action", "id": "coordinated-transmission-q02" } ] } ] } ] }, { "id": "accuracy-and-completion", "name": "Accuracy and completion", "description": "Assesses the fidelity of reception and the evidence for successful communication.", "rationale": "An agent needs separate grounds for trusting a transcription and declaring a message delivered.", "layers": [ { "id": "reception-and-correction", "name": "Reception and correction", "description": "Preserves ambiguity and records the procedures used to detect and repair errors.", "findings": [ { "id": "supported-transcription", "name": "Supported transcription", "description": "Keep uncertain groups distinguishable from confirmed text and record any repetition, comparison or system-supported checking procedure.", "questions": [ { "text": "Which received characters or groups remain uncertain, and how was their uncertainty identified?", "kind": "measurement", "id": "supported-transcription-q01" }, { "text": "Which correction or repeat procedure is available, and what evidence will resolve the uncertainty?", "kind": "action", "id": "supported-transcription-q02" } ] } ] }, { "id": "delivery-evidence", "name": "Delivery evidence", "description": "Separates completion of signalling from receipt, acceptance and delivery to an addressee.", "findings": [ { "id": "bounded-completion-claim", "name": "Bounded completion claim", "description": "Assign message status only to the stage supported by logs, acknowledgements or delivery records, preserving unknown outcomes.", "questions": [ { "text": "Does the available evidence establish transmission, station receipt, acceptance or final delivery?", "kind": "provenance", "id": "bounded-completion-claim-q01" }, { "text": "When acknowledgement is absent, what retry or inquiry procedure applies and how are duplicates recognised?", "kind": "action", "id": "bounded-completion-claim-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": [ "This describes telegraphy as an activity and communication method, consistent with ACT.ACT; no narrower registry sense was supplied.", "Historical technical classifications sometimes include facsimile under telegraphy, while ordinary accounts focus on character-based messages.", "Standards are recalled by designation without checking editions or current status; operating speeds are illustrative rather than defining limits." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of telegraphy this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-kinds", "name": "Kinds and varieties", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Optical telegraphy, including semaphore systems", "Wired electrical telegraphy", "Submarine cable telegraphy", "Radiotelegraphy", "Printing telegraphy, including teleprinters", "Facsimile telegraphy, in historical technical classifications" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of telegraphy 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": [ "ITU-R Recommendation M.1677 specifies International Morse code.", "ITU-T Recommendation S.1 specifies International Telegraph Alphabet No. 2.", "ITU Radio Regulations govern radio spectrum use, including stations using radiotelegraphy." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of telegraphy 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": [ "Historically, commercial telegram services carried personal, business and government messages.", "Railways used telegraph networks to coordinate operations and communicate train movements.", "Submarine telegraph cables supported intercontinental communication.", "Maritime services historically used radiotelegraphy for operational and distress communication.", "Amateur radio operators use Morse radiotelegraphy for communication, training and contests." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of telegraphy this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "quantity": "Manual Morse transmission speed", "typical_range": "Approximately 10-30 in ordinary trained operation; learners and specialist high-speed operators fall outside this range", "unit": "words per minute, commonly using the PARIS reference word" }, { "quantity": "Teleprinter modulation rate", "typical_range": "Historical systems commonly used nominal rates of 45.45, 50 or 75", "unit": "baud" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of telegraphy 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": [ "Noise, interference or fading can obscure signals or produce character errors.", "Incorrect timing, spacing or transcription can change message meaning.", "Cable breaks, power loss or relay failures can interrupt service.", "Optical systems depend on visibility and an unobstructed line of sight.", "Unauthenticated or unencrypted messages can be intercepted, forged or altered." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of telegraphy this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "American Morse and International Morse used different character codes; historical American landline practice must be distinguished from international practice.", "Teleprinter services adopted national character assignments and adaptations for different writing systems.", "Optical telegraph networks used different national apparatus and codebooks." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of telegraphy 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": "telegraph", "difference": "A telegraph is an apparatus or system; telegraphy is the communication method and practice." }, { "name": "Morse code", "difference": "Morse code is one encoding system used in telegraphy; telegraphy also uses other codes and signalling systems." }, { "name": "telephony", "difference": "Telephony conveys speech for listening, whereas telegraphy conveys coded messages for interpretation or recording." }, { "name": "telegram", "difference": "A telegram is a message handled by a telegraph service, rather than the communication method itself." }, { "name": "telex", "difference": "Telex is a switched subscriber teleprinter service and therefore a particular application of telegraphy." }, { "name": "data communication", "difference": "Data communication includes general machine-readable information exchange; telegraphy conventionally denotes a historically established class of coded-message systems." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of telegraphy this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which authoritative definition should govern this registry entry, particularly the inclusion of facsimile, teleprinters and digital data transmission?", "Does an existing Vercy world model already cover telegraphy or own part of this activity, requiring a link or narrower scope?", "Which optical, wired and radio systems must research sample to avoid treating Morse operating conventions as universal?", "Which rate and accuracy measures allow useful comparison across manual and automatic systems without concealing incompatible conventions?", "Which service-specific rules establish acknowledgement, retry, priority and final delivery, and which remain undocumented?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 28 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "abstract concept", "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 telegraphy, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise a telegraphic communication practice, assess whether a message can be conveyed and interpreted reliably, and determine the next appropriate operating action.", "characteristics": { "substance": "activity", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: wireless telegraphy, flag semaphore, alphabetical telegraphy, International Code of Signals, High Speed Telegraphy.", "5 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 82 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 telegraphy, and on what evidence are they told apart?" ], "whatItIsMadeOf": "something that happens over time", "physicalCharacter": [ "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": [ "Nothing to see. What is recognised is an instance of it, and which instances count is exactly what is argued about." ], "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": [ "wireless telegraphy", "flag semaphore", "alphabetical telegraphy", "International Code of Signals", "High Speed Telegraphy" ] } ], "standing": "Described in 82 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 5 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 telegraphy from another, and a telegraphy 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 telegraphy, 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 telegraphy, 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 telegraphy 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 telegraphy, 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 telegraphy, 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 telegraphy 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 telegraphy 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 telegraphy, 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 telegraphy, 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 telegraphy 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 telegraphy from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a telegraphy, 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 telegraphy, 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 telegraphy 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 telegraphy 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 telegraphy between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a telegraphy, 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 telegraphy, 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 telegraphy 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 telegraphy, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a telegraphy 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 telegraphy, 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 telegraphy, 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 telegraphy is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "process-and-outcome", "name": "Process, inputs and outcome", "description": "How a telegraphy proceeds, what it needs and what it leaves behind.", "rationale": "An activity is known by its steps and its results, and both have to be recordable while it is still running.", "layers": [ { "id": "steps-and-sequence", "name": "Steps and sequence", "description": "The steps of a telegraphy, their order and what may run in parallel.", "findings": [ { "id": "steps-and-preconditions", "name": "Steps, preconditions and completion", "description": "What has to be true before each step of a telegraphy and what marks it done.", "questions": [ { "id": "steps-and-preconditions-q01", "text": "What identifies and describes a step of a telegraphy, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "steps-and-preconditions-q02", "text": "Who or what asserted this about a step of a telegraphy, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "steps-and-preconditions-q03", "text": "What may an agent decide or do once a step of a telegraphy is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "inputs-and-results", "name": "Inputs, resources and results", "description": "What a telegraphy consumes and what it produces.", "findings": [ { "id": "inputs-and-outputs", "name": "Inputs, outputs and side effects", "description": "The resources a telegraphy takes and the results it leaves, wanted or not.", "questions": [ { "id": "inputs-and-outputs-q01", "text": "What identifies and describes the inputs and results of a telegraphy, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "inputs-and-outputs-q02", "text": "Who or what asserted this about the inputs and results of a telegraphy, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "inputs-and-outputs-q03", "text": "What may an agent decide or do once the inputs and results of a telegraphy is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "definitions-in-contest", "name": "Definitions and who holds them", "description": "What telegraphy is taken to mean, and by whom.", "rationale": "When a field disagrees about a concept, the disagreement is the content. A model that picks one definition silently destroys the information.", "layers": [ { "id": "competing-definitions", "name": "Competing definitions", "description": "The main readings and the traditions behind them.", "findings": [ { "id": "definition-map", "name": "Definitions and their holders", "description": "Each definition with the school or body that holds it.", "questions": [ { "id": "definition-map-q01", "text": "Which definitions of telegraphy are in use, and which tradition or body holds each?", "kind": "definition" }, { "id": "definition-map-q02", "text": "What turns on the difference between them in practice?", "kind": "boundary" } ] } ] }, { "id": "operationalisation", "name": "Operationalisation", "description": "How it is measured or applied when it has to be.", "findings": [ { "id": "operational-record", "name": "Measures and proxies", "description": "Instruments and indicators used to stand in for it.", "questions": [ { "id": "operational-record-q01", "text": "How is telegraphy operationalised or measured in practice, and by what instrument?", "kind": "measurement" }, { "id": "operational-record-q02", "text": "What does that operationalisation leave out, and when does that matter?", "kind": "boundary" } ] } ] } ] }, { "id": "instances-and-use", "name": "Instances, use and consequence", "description": "What counts as an instance of telegraphy and what follows from calling something that.", "rationale": "Applying a concept is an act with consequences, so a model must say what the label licenses and what it does not.", "layers": [ { "id": "instances", "name": "What counts as an instance", "description": "Clear cases, borderline cases and non-cases.", "findings": [ { "id": "instance-tests", "name": "Tests for an instance", "description": "What would settle whether something falls under it.", "questions": [ { "id": "instance-tests-q01", "text": "What would settle whether something is an instance of telegraphy?", "kind": "boundary" }, { "id": "instance-tests-q02", "text": "Which borderline cases are argued about, and on what grounds?", "kind": "definition" } ] } ] }, { "id": "consequence", "name": "Consequence of application", "description": "Rights, duties or decisions that follow from the label.", "findings": [ { "id": "consequence-record", "name": "What the label licenses", "description": "What an agent may do once something is classified this way.", "questions": [ { "id": "consequence-record-q01", "text": "What follows practically once something is treated as telegraphy?", "kind": "action" }, { "id": "consequence-record-q02", "text": "What must an agent not infer from the label alone?", "kind": "action" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a telegraphy 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 telegraphy and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a telegraphy, 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 telegraphy, 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 telegraphy 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 telegraphy is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a telegraphy, 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 telegraphy, 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 telegraphy is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 6, "layers": 12, "findings": 14, "questions": 38 } } } }