{ "model": { "rank": 4557, "code": "thing-q132744", "model_id": "vr.tr.fax", "name": "fax", "purpose": "Enable an agent to recognise a fax as a page-oriented facsimile communication, assess its completeness and delivery state, and determine appropriate handling or retransmission.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.KNW", "industry": "", "version": "", "url": "/models/thing/q132744/", "tier": 2, "score": 74, "payload": { "layer": "wikidata", "aliases": [ "Sealfax", "Group 1 fax machine", "Fultograph", "black fax" ], "aliasCount": 4, "merged": 4, "knownIn": 74, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q132744", "url": "https://www.wikidata.org/wiki/Q132744", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T20:30:05Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 22, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a087dc-1dd2-7c80-92ed-09367817f652\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: fax\nSense to describe: (none recorded)\nDomain code: INF.KNW\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 005: 1001 registered ", "usd": 0, "recall": true }, "codex": { "seconds": 60.9, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a087dc-1dc4-7673-a4c9-82b7971e9bbf\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: fax\nRegistry id: vr.tr.fax\nPlane / domain: INF / INF.KNW\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nContext for this" } } }, "metaModel": { "id": "THING-Q132744", "registryId": "vr.tr.fax", "name": "fax", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.KNW" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q132744/", "model": { "registry_id": "vr.tr.fax", "name": "fax", "purpose": "Enable an agent to recognise a fax as a page-oriented facsimile communication, assess its completeness and delivery state, and determine appropriate handling or retransmission.", "definition": "Fax, or facsimile transmission, is a telecommunications method that transmits an encoded image of a document to a remote receiver for reproduction on paper or as an electronic image.", "scope_statement": "This model owns fax in its informational sense: a document communicated through a facsimile exchange, including its page representation, addressing, transmission evidence and received rendition; fax machines and services are supporting entities.", "in_scope": [ "Fax document identity, intended communication and page sequence", "Source and received page representations and their fidelity", "Sender, recipient and fax endpoint associations", "Transmission attempts, reception evidence and failure states", "Access, retention and handling requirements attached to fax content" ], "out_of_scope": [ "Fax machine construction, maintenance and physical inventory", "Telephone networks, numbering plans and general telecommunications infrastructure", "Fax service providers as organisations or commercial products", "The substantive case, transaction or business process discussed in the document", "General document authoring, scanning and optical character recognition systems" ], "distinguishing_features": [ "A fax has an asserted facsimile transmission context; a scanned document alone does not establish that it is a fax.", "Its communicated content is organised as page images; extracted text is a derivative representation that may omit visual information.", "A fax number or endpoint identifies a delivery destination but does not by itself establish the identity of the person receiving or reading it.", "A transmission report describes an exchange or attempt and must be distinguished from the communicated document.", "A fax machine is an apparatus that sends or receives faxes; an electronic fax rendition can exist without a paper copy." ], "characteristics": [ { "name": "Fax representation role", "kind": "category", "unit_or_values": "source document | submitted fax rendition | received fax rendition | transmission report | extracted derivative", "why_it_matters": "Prevents a report, source file or OCR output from being mistaken for the received communication." }, { "name": "Page count reconciliation", "kind": "measurement", "unit_or_values": "pages expected, submitted and received; unknown allowed for each", "why_it_matters": "Exposes missing pages and disagreements over whether a cover sheet is included." }, { "name": "Page imaging resolution", "kind": "measurement", "unit_or_values": "horizontal and vertical samples per inch or per millimetre, with representation identified", "why_it_matters": "Helps assess preservation of small text, signatures and fine graphical details." }, { "name": "Received page condition", "kind": "state", "unit_or_values": "unchecked | legible | partially legible | illegible; clipping, missing regions and orientation recorded separately", "why_it_matters": "Successful transport does not guarantee usable document content." }, { "name": "Endpoint and party association", "kind": "relation", "unit_or_values": "sending or receiving endpoint linked to an asserted party, verification evidence and observation time", "why_it_matters": "Separates routing information from verified sender or recipient identity." }, { "name": "Transmission path", "kind": "category", "unit_or_values": "telephone fax | IP fax | service-mediated fax | mixed | unknown", "why_it_matters": "Locates conversions and handoffs that affect available delivery evidence." }, { "name": "Attempt outcome", "kind": "state", "unit_or_values": "queued | attempting | reported successful | reported failed | indeterminate", "why_it_matters": "Supports recovery without treating reported transport success as human acknowledgement." }, { "name": "Recipient acknowledgement", "kind": "state", "unit_or_values": "none recorded | receipt acknowledged | readability acknowledged | disputed", "why_it_matters": "Distinguishes endpoint reception from confirmation by the intended recipient." }, { "name": "Handling constraints", "kind": "relation", "unit_or_values": "applicable access, routing, retention and disposal instructions linked to their authority", "why_it_matters": "Guides handling of copies across fax inboxes, printouts and downstream systems." } ], "affordances": [ "Compare submitted and received page sets for omissions, ordering errors and degraded content.", "Validate the intended recipient's association with the destination fax endpoint before dispatch.", "Prepare and submit a page rendition through an authorised fax endpoint.", "Interpret transmission reports while preserving uncertainty about human receipt.", "Retry failed or incomplete transmissions with explicit links to earlier attempts.", "Route, retain or dispose of received fax copies according to applicable handling instructions." ] }, "sources": [], "structure": { "bundles": [ { "id": "fax-identity-and-boundaries", "name": "Fax identity and boundaries", "description": "Establishes which communication and representations constitute the fax being modelled.", "rationale": "The word fax can identify a document, an exchange or an apparatus; agents need an explicit informational boundary.", "layers": [ { "id": "communication-identity", "name": "Communication identity", "description": "Identifies the intended page-oriented communication independently of individual attempts.", "findings": [ { "id": "fax-communication-boundary", "name": "Fax communication boundary", "description": "Record the intended message and the evidence that places it within a facsimile exchange.", "questions": [ { "text": "What document or page set is intended to constitute this fax?", "kind": "definition", "id": "fax-communication-boundary-q01" }, { "text": "What evidence establishes fax transmission rather than scanning or ordinary file transfer?", "kind": "boundary", "id": "fax-communication-boundary-q02" } ] } ] }, { "id": "representation-lineage", "name": "Representation lineage", "description": "Connects source files, submitted pages, received renditions and derivatives.", "findings": [ { "id": "rendition-and-report-separation", "name": "Rendition and report separation", "description": "Identify each artifact's role and preserve its relationship to the communication and transmission attempt.", "questions": [ { "text": "Is this artifact the source, submitted rendition, received rendition, report or an extracted derivative?", "kind": "definition", "id": "rendition-and-report-separation-q01" }, { "text": "Which conversion, reception or extraction produced this artifact, and from which predecessor?", "kind": "provenance", "id": "rendition-and-report-separation-q02" } ] } ] } ] }, { "id": "page-integrity-and-readability", "name": "Page integrity and readability", "description": "Describes whether the received fax preserves the intended page content in usable form.", "rationale": "Fax completion must account for page omissions and image degradation, not only transmission status.", "layers": [ { "id": "page-set-reconciliation", "name": "Page set reconciliation", "description": "Compares expected, submitted and received page sequences.", "findings": [ { "id": "page-count-and-order", "name": "Page count and order", "description": "Record page totals, ordering and the treatment of cover sheets, blank pages and repeated pages.", "questions": [ { "text": "How many pages were expected, submitted and received, and does each total include the cover sheet?", "kind": "measurement", "id": "page-count-and-order-q01" }, { "text": "Which received pages are missing, repeated, out of order or unmatched to the submitted rendition?", "kind": "measurement", "id": "page-count-and-order-q02" } ] } ] }, { "id": "image-fidelity", "name": "Image fidelity", "description": "Assesses losses introduced by scanning, conversion, transport or output.", "findings": [ { "id": "critical-content-legibility", "name": "Critical content legibility", "description": "Assess whether text and visual marks needed for the fax's purpose remain interpretable.", "questions": [ { "text": "Which pages or regions show clipping, streaking, low contrast, distortion or unreadable detail?", "kind": "measurement", "id": "critical-content-legibility-q01" }, { "text": "Do defects obscure information needed to act on this fax, such as amounts, identifiers or signature marks?", "kind": "action", "id": "critical-content-legibility-q02" }, { "text": "Which source and received renditions are available for a direct fidelity comparison?", "kind": "provenance", "id": "critical-content-legibility-q03" } ] } ] } ] }, { "id": "fax-addressing-and-handoffs", "name": "Fax addressing and handoffs", "description": "Connects intended parties to fax endpoints and identifies service or network transitions.", "rationale": "A correctly dialled endpoint can still route to the wrong person, and service acceptance can precede actual fax delivery.", "layers": [ { "id": "party-endpoint-binding", "name": "Party endpoint binding", "description": "Separates asserted identities, dialled destinations and verified endpoint ownership or use.", "findings": [ { "id": "destination-and-sender-evidence", "name": "Destination and sender evidence", "description": "Record how endpoints and displayed sender identifiers are associated with the relevant parties.", "questions": [ { "text": "Which destination was used, and how was its association with the intended recipient verified?", "kind": "provenance", "id": "destination-and-sender-evidence-q01" }, { "text": "Which sender identity claims come from document content, displayed fax identifiers or independent verification?", "kind": "provenance", "id": "destination-and-sender-evidence-q02" }, { "text": "Does the destination serve a shared inbox or machine requiring additional recipient routing?", "kind": "boundary", "id": "destination-and-sender-evidence-q03" } ] } ] }, { "id": "transmission-handoffs", "name": "Transmission handoffs", "description": "Identifies observable stages between submission and the recipient's accessible copy.", "findings": [ { "id": "service-and-endpoint-stages", "name": "Service and endpoint stages", "description": "Record known gateways, fax endpoints and subsequent inbox or print delivery stages.", "questions": [ { "text": "Which stages are known between submitting the document and making the received copy available?", "kind": "provenance", "id": "service-and-endpoint-stages-q01" }, { "text": "At which stage does each available acceptance or delivery report apply?", "kind": "boundary", "id": "service-and-endpoint-stages-q02" } ] } ] } ] }, { "id": "delivery-evidence-and-recovery", "name": "Delivery evidence and recovery", "description": "Tracks fax attempts, interprets their evidence and supports controlled retransmission.", "rationale": "Fax exchanges can fail, partly complete or produce uncertain outcomes that make retries create duplicate communications.", "layers": [ { "id": "attempt-evidence", "name": "Attempt evidence", "description": "Records attempt-specific results without overstating what they prove.", "findings": [ { "id": "reported-outcome-and-acknowledgement", "name": "Reported outcome and acknowledgement", "description": "Separate transport reports, page reception evidence and recipient acknowledgement.", "questions": [ { "text": "What outcome, timestamp, page total and error information does the report record for this attempt?", "kind": "measurement", "id": "reported-outcome-and-acknowledgement-q01" }, { "text": "What does the reporting system define as success, and is recipient acknowledgement recorded separately?", "kind": "definition", "id": "reported-outcome-and-acknowledgement-q02" } ] } ] }, { "id": "retransmission-control", "name": "Retransmission control", "description": "Relates repeat attempts to prior deliveries and content revisions.", "findings": [ { "id": "retry-scope-and-duplicate-risk", "name": "Retry scope and duplicate risk", "description": "Determine what needs resending and make repeated or corrected communications recognisable.", "questions": [ { "text": "Does the evidence support resending the entire fax, selected pages or a corrected rendition?", "kind": "action", "id": "retry-scope-and-duplicate-risk-q01" }, { "text": "How will the recipient distinguish this retry from a new instruction or an additional transaction?", "kind": "action", "id": "retry-scope-and-duplicate-risk-q02" }, { "text": "Which earlier attempts and document versions does the retransmission repeat or supersede?", "kind": "provenance", "id": "retry-scope-and-duplicate-risk-q03" } ] } ] } ] }, { "id": "fax-copy-handling", "name": "Fax copy handling", "description": "Controls the exposure and continuing use of fax renditions and associated evidence.", "rationale": "Fax reception can create paper and electronic copies in shared locations with different access and retention conditions.", "layers": [ { "id": "recipient-access", "name": "Recipient access", "description": "Assesses who can access the received fax and how it reaches the intended recipient.", "findings": [ { "id": "shared-reception-exposure", "name": "Shared reception exposure", "description": "Record access conditions for receiving devices, service inboxes, forwarding destinations and printouts.", "questions": [ { "text": "Who can access the receiving inbox, machine output or automatically forwarded copy?", "kind": "boundary", "id": "shared-reception-exposure-q01" }, { "text": "What authorised routing or collection action is needed to place the fax with its intended recipient?", "kind": "action", "id": "shared-reception-exposure-q02" } ] } ] }, { "id": "copy-retention-and-evidence", "name": "Copy retention and evidence", "description": "Links retained fax renditions and reports to applicable handling instructions.", "findings": [ { "id": "retained-rendition-selection", "name": "Retained rendition selection", "description": "Identify which copies and reports support future use or review and what governs their retention.", "questions": [ { "text": "Which received rendition and transmission evidence must remain linked for later review?", "kind": "action", "id": "retained-rendition-selection-q01" }, { "text": "Which documented policy or instruction governs retention and disposal of fax images, reports and paper copies?", "kind": "provenance", "id": "retained-rendition-selection-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": [ "The name can denote the transmission method, an apparatus or a received document; this description covers the method.", "This is recall-based information, with no sources consulted; standard editions and jurisdiction-specific requirements need verification.", "The measurement values describe common Group 3 capabilities, not every fax implementation or negotiated connection." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of fax 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": [ "Group 3 fax", "Group 4 fax", "Fax over IP", "Internet fax services" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of fax this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "scheme": "ITU-T E.164", "value_or_pattern": "International telephone number with at most 15 digits", "note": "Identifies a fax endpoint reached through the telephone network; it does not identify an individual document." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of fax 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-T T.30 specifies procedures for document facsimile transmission in the general switched telephone network.", "ITU-T T.4 specifies Group 3 facsimile terminal characteristics, including image coding.", "ITU-T T.6 specifies Group 4 facsimile image coding schemes.", "ITU-T T.38 specifies procedures for real-time Group 3 facsimile communication over IP networks.", "ITU-T T.37 specifies store-and-forward facsimile transmission over the Internet." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of fax 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": [ "Exchanging scanned forms and signed documents between organisations.", "Transmitting referrals, prescriptions and other healthcare documents where fax workflows are supported.", "Submitting administrative documents to offices that accept fax.", "Connecting legacy fax machines to digital messaging and document-management services." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of fax 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": "Group 3 modem data rate", "typical_range": "2.4-33.6", "unit": "kbit/s" }, { "quantity": "Common Group 3 horizontal sampling density", "typical_range": "8", "unit": "pixels/mm" }, { "quantity": "Common Group 3 vertical sampling density in standard and fine modes", "typical_range": "3.85-7.7", "unit": "lines/mm" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of fax 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": [ "An incorrect destination number can disclose confidential documents.", "Line noise, disconnections or incompatible gateways can interrupt transmission or damage received images.", "Low resolution and bilevel image conversion can obscure small print, handwriting and shaded content.", "Paper jams, depleted consumables or unattended output trays can prevent retrieval or expose documents.", "A transmission confirmation does not establish that the intended person read the document." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of fax 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": [ "Dialling conventions and telephone-network interfaces vary by country.", "Acceptance of faxed documents and signatures depends on jurisdiction, institution and document type.", "Reliance on fax differs across countries and sectors, particularly in healthcare and public administration." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of fax 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": "fax machine", "difference": "The machine is a physical endpoint implementing fax; fax is the transmission method." }, { "name": "scanner", "difference": "A scanner digitises a document locally; fax additionally communicates its image to a remote endpoint." }, { "name": "email", "difference": "Email exchanges electronic messages and attachments; fax uses facsimile transmission conventions, although services can bridge the two." }, { "name": "photocopier", "difference": "A photocopier reproduces a document locally without requiring remote transmission." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of fax this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend fax to mean the communicated document, the communication method or the apparatus, and does an existing world model already own any of these senses?", "Which fax standards and service interfaces should supply authoritative definitions of page acceptance, successful completion and error outcomes?", "How should communication identity be preserved when retries send only missing pages or incorporate corrected content?", "Which use-specific criteria establish adequate readability and fidelity for acting on a received fax?", "Which organisational or jurisdictional requirements govern recipient verification, evidentiary use and retention in the intended deployment?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 19, "questions": 32 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "discipline or field of knowledge", "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 fax, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise a fax as a page-oriented facsimile communication, assess its completeness and delivery state, and determine appropriate handling or retransmission.", "characteristics": { "substance": "information", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "read and interpreted" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: Sealfax, Group 1 fax machine, Fultograph, black fax.", "4 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 74 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 fax, and on what evidence are they told apart?" ], "whatItIsMadeOf": "content that has to be carried by something else", "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": [ "read it and act on what it says" ], "howItIsRecognised": [], "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": [ "Sealfax", "Group 1 fax machine", "Fultograph", "black fax" ] } ], "standing": "Described in 74 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 4 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 fax from another, and a fax 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 fax, 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 fax, 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 fax 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 fax, 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 fax, 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 fax 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 fax 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 fax, 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 fax, 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 fax 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 fax from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a fax, 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 fax, 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 fax 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 fax 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 fax between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a fax, 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 fax, 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 fax 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 fax, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a fax 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 fax, 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 fax, 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 fax is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "content-and-access", "name": "Content, encoding and access", "description": "What a fax says, how it is encoded and who may read it.", "rationale": "An informational thing carries content that can be copied, versioned and withheld, none of which its physical carrier explains.", "layers": [ { "id": "content-and-encoding", "name": "Content and encoding", "description": "The content itself, its format and its language.", "findings": [ { "id": "content-and-format", "name": "Content, format and language", "description": "What a fax contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a fax, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "content-and-format-q02", "text": "Who or what asserted this about the content of a fax, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "content-and-format-q03", "text": "What may an agent decide or do once the content of a fax is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "access-and-rights", "name": "Access, rights and retention", "description": "Who may read, copy or change it, and for how long it is kept.", "findings": [ { "id": "access-rules", "name": "Access rules and retention", "description": "The permissions attached to a fax and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a fax, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "access-rules-q02", "text": "Who or what asserted this about access to a fax, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "access-rules-q03", "text": "What may an agent decide or do once access to a fax is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "subject-and-method", "name": "Subject matter and method", "description": "What fax studies and how it establishes anything.", "rationale": "A field is identified by its questions and its methods, and those are what distinguish it from the fields next to it.", "layers": [ { "id": "subject", "name": "Subject matter", "description": "The questions it takes as its own.", "findings": [ { "id": "subject-record", "name": "Questions and objects of study", "description": "What it is about, stated so a neighbouring field can be told apart.", "questions": [ { "id": "subject-record-q01", "text": "What questions and objects does fax take as its own?", "kind": "definition" }, { "id": "subject-record-q02", "text": "Which questions does it share with a neighbouring field, and who claims them?", "kind": "boundary" } ] } ] }, { "id": "method", "name": "Method and evidence", "description": "How claims are established and what counts as evidence.", "findings": [ { "id": "method-record", "name": "Methods and standards of evidence", "description": "The methods used and what they are taken to establish.", "questions": [ { "id": "method-record-q01", "text": "By what methods does fax establish claims, and what counts as sufficient evidence?", "kind": "provenance" }, { "id": "method-record-q02", "text": "What kind of claim can this field not settle, and where should an agent look instead?", "kind": "action" } ] } ] } ] }, { "id": "institutions-and-classification", "name": "Institutions and classification", "description": "Where fax is practised and how catalogues place it.", "rationale": "The institutional footprint is the evidence that a field exists as a field rather than as a topic.", "layers": [ { "id": "institutions", "name": "Institutional markers", "description": "Societies, journals, degrees and departments.", "findings": [ { "id": "institution-record", "name": "Bodies and venues", "description": "Where the field organises itself.", "questions": [ { "id": "institution-record-q01", "text": "Which societies, journals or degrees mark fax as an established field?", "kind": "provenance" }, { "id": "institution-record-q02", "text": "What would show that it is emerging or dissolving rather than established?", "kind": "boundary" } ] } ] }, { "id": "classification", "name": "Classification schemes", "description": "Where library and research classifications put it.", "findings": [ { "id": "classification-record", "name": "Codes and their disagreements", "description": "The classification codes that place it, and where they differ.", "questions": [ { "id": "classification-record-q01", "text": "Which classification schemes place fax, under what codes?", "kind": "definition" }, { "id": "classification-record-q02", "text": "Where do those schemes disagree about its scope?", "kind": "boundary" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a fax 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 fax and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a fax, 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 fax, 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 fax 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 fax is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a fax, 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 fax, 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 fax 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 } } } }