{ "model": { "rank": 4622, "code": "thing-q4885200", "model_id": "vr.tr.windows-phone", "name": "Windows Phone", "purpose": "Enable an agent to recognise a Windows Phone handset, assess its hardware and software state, and determine which uses, repairs and data-preservation actions remain feasible.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q4885200/", "tier": 2, "score": 74, "payload": { "layer": "wikidata", "aliases": [ "Windows Phone 8.1", "Windows 10 Mobile", "Windows Phone 8" ], "aliasCount": 3, "merged": 3, "knownIn": 74, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q4885200", "url": "https://www.wikidata.org/wiki/Q4885200", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T20:38:42Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 18.4, "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: 01a087e4-0f8e-7aa2-b5b3-00ef4ed739bb\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Windows Phone\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 005: 1001 r", "usd": 0, "recall": true }, "codex": { "seconds": 57.1, "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: 01a087e4-0f8e-7860-81db-cd0f87a59163\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Windows Phone\nRegistry id: vr.tr.windows-phone\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none" } } }, "metaModel": { "id": "THING-Q4885200", "registryId": "vr.tr.windows-phone", "name": "Windows Phone", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q4885200/", "model": { "registry_id": "vr.tr.windows-phone", "name": "Windows Phone", "purpose": "Enable an agent to recognise a Windows Phone handset, assess its hardware and software state, and determine which uses, repairs and data-preservation actions remain feasible.", "definition": "Windows Phone is Microsoft's discontinued family of proprietary smartphone operating systems, comprising Windows Phone 7, 8 and 8.1, rather than a particular physical handset.", "scope_statement": "This model provisionally interprets vr.tr.windows-phone in PHY / PHY.OBJ as the kind of physical smartphone associated with Microsoft's Windows Phone platform; it owns platform-specific handset identity, dependencies and operating constraints, while leaving the intended registry sense and inclusion of Windows 10 Mobile handsets unresolved.", "in_scope": [ "Handset identity and evidence of its Windows Phone platform association", "Installed operating-system release, firmware and supported hardware relationship", "Platform-specific navigation, applications, accounts and service dependencies", "Cellular compatibility and present-day standalone or connected usability", "Recovery, repair, data extraction and retirement constraints" ], "out_of_scope": [ "Windows Phone as a software platform considered independently of physical handsets", "Individual handset inventory records and ownership histories", "Manufacturer product lines and their commercial histories", "Generic smartphone engineering already covered by a broader smartphone model", "Windows desktop computers, tablets and unrelated Windows-branded devices", "Carrier networks and Microsoft services as independently operated systems" ], "distinguishing_features": [ "Require a model identifier or reliable software record linking the handset to Windows Phone; visual styling or a Windows-themed launcher alone is insufficient.", "Distinguish a handset's original platform from its currently installed system, including upgrades or unofficial modifications.", "Do not treat Nokia or Lumia branding alone as proof of the installed operating system.", "Separate Windows Phone lineage from older Windows Mobile devices and flag Windows 10 Mobile devices for an explicit scope decision.", "Identify a physical handset with telephone hardware rather than an emulator, operating-system image or software licence." ], "characteristics": [ { "name": "Handset platform identity", "kind": "relation", "unit_or_values": "manufacturer and model identifier linked to documented original platform", "why_it_matters": "Establishes membership without relying on branding or appearance." }, { "name": "Installed software identity", "kind": "category", "unit_or_values": "OS family, release, build, firmware revision and official or modified status", "why_it_matters": "Determines which compatibility and recovery claims apply." }, { "name": "Boot and access condition", "kind": "state", "unit_or_values": "operational and unlocked; operational and locked; recovery mode; boot loop; no power; unknown", "why_it_matters": "Constrains inspection, extraction and restoration actions." }, { "name": "Application execution compatibility", "kind": "relation", "unit_or_values": "application or package linked to OS release, installation route and tested result", "why_it_matters": "Separates an application's historical availability from present installability and operation." }, { "name": "Service dependency condition", "kind": "state", "unit_or_values": "per feature: tested working; partially working; unavailable; untested, with date", "why_it_matters": "A working handset may still depend on unavailable authentication, distribution or content services." }, { "name": "Cellular capability and eligibility", "kind": "relation", "unit_or_values": "radio bands and technologies linked to carrier, SIM restrictions and dated voice/data test", "why_it_matters": "Radio specifications alone do not establish current network usability." }, { "name": "Battery condition", "kind": "measurement", "unit_or_values": "observed runtime in hours under a stated workload; measured capacity in mAh when obtainable", "why_it_matters": "Supports practical usability and repair decisions without assuming diagnostic access." }, { "name": "Data recoverability", "kind": "state", "unit_or_values": "per data class: locally exportable; account-dependent; application-dependent; inaccessible; unknown", "why_it_matters": "Determines what must be preserved before reset, firmware recovery or retirement." } ], "affordances": [ "Identify the handset and relate its original platform to its installed software.", "Evaluate a specified application or workflow against the actual OS build and available services.", "Test cellular and offline functions under recorded conditions.", "Select a compatible repair or recovery route using model-specific evidence.", "Export accessible personal data before destructive maintenance.", "Classify the handset for continued use, archival preservation, parts recovery or recycling." ] }, "sources": [], "structure": { "bundles": [ { "id": "platform-and-handset-identity", "name": "Platform and handset identity", "description": "Establish what makes the physical handset a Windows Phone and which platform generation governs it.", "rationale": "The name can denote software, a handset category or adjacent mobile-platform generations, each with different boundaries.", "layers": [ { "id": "registry-sense-and-membership", "name": "Registry sense and membership", "description": "Resolve the physical-device interpretation and its platform boundaries.", "findings": [ { "id": "physical-platform-membership", "name": "Physical platform membership", "description": "Record evidence that a handset belongs to the intended Windows Phone category and flag cases whose lineage does not settle membership.", "questions": [ { "text": "Does the registry entry denote physical Windows Phone handsets or the operating-system family despite its PHY.OBJ classification?", "kind": "boundary", "id": "physical-platform-membership-q01" }, { "text": "Which manufacturer documentation or device identifiers establish this handset's original operating-system family?", "kind": "provenance", "id": "physical-platform-membership-q02" } ] } ] }, { "id": "software-and-hardware-pairing", "name": "Software and hardware pairing", "description": "Connect the installed software to the exact hardware variant.", "findings": [ { "id": "release-and-firmware-identity", "name": "Release and firmware identity", "description": "Keep original OS, installed OS, firmware and hardware variant distinct so that upgrade or modification history does not obscure compatibility.", "questions": [ { "text": "Which OS family, version, build and firmware revision can be read from the handset or recovery interface?", "kind": "measurement", "id": "release-and-firmware-identity-q01" }, { "text": "Is that combination documented for this model and carrier variant, or does it reflect an unofficial modification?", "kind": "provenance", "id": "release-and-firmware-identity-q02" } ] } ] } ] }, { "id": "interaction-and-application-viability", "name": "Interaction and application viability", "description": "Assess the handset's Windows Phone interface and the applications it can actually run.", "rationale": "Platform appearance, application compatibility and installation availability are separate conditions that an agent must test.", "layers": [ { "id": "navigation-and-local-functions", "name": "Navigation and local functions", "description": "Assess platform navigation and useful functions without assuming connected services.", "findings": [ { "id": "interface-operability", "name": "Interface operability", "description": "Record operation of the Start screen, tiles and release-specific navigation controls, alongside local functions required for the intended use.", "questions": [ { "text": "Can the user unlock the phone, navigate Start and the application list, and operate the navigation controls present on this variant?", "kind": "action", "id": "interface-operability-q01" }, { "text": "Which required functions, such as camera capture or local media playback, work with network access disabled?", "kind": "measurement", "id": "interface-operability-q02" } ] } ] }, { "id": "application-installation-and-execution", "name": "Application installation and execution", "description": "Determine whether a specific application can be obtained, installed and used on the recorded release.", "findings": [ { "id": "application-viability-evidence", "name": "Application viability evidence", "description": "Record package compatibility, installation prerequisites and execution results separately from historical catalogue listings.", "questions": [ { "text": "What evidence establishes that the required application version supports this OS build and hardware?", "kind": "provenance", "id": "application-viability-evidence-q01" }, { "text": "Can it currently be installed or reinstalled through an available authorised route, and does its required workflow complete?", "kind": "action", "id": "application-viability-evidence-q02" } ] } ] } ] }, { "id": "network-and-service-dependencies", "name": "Network and service dependencies", "description": "Determine whether the handset's radios and platform-dependent services support its intended use now.", "rationale": "A legacy handset can boot and launch applications while network access, account sign-in or remote features fail independently.", "layers": [ { "id": "carrier-and-radio-operation", "name": "Carrier and radio operation", "description": "Relate the exact handset variant to a specific carrier and location.", "findings": [ { "id": "current-telephony-usability", "name": "Current telephony usability", "description": "Record dated evidence for voice, messaging and data operation instead of inferring service from a signal indicator or supported bands.", "questions": [ { "text": "Which documented radio technologies, bands, SIM restrictions and carrier provisioning requirements apply to this hardware variant?", "kind": "provenance", "id": "current-telephony-usability-q01" }, { "text": "On the intended carrier and at the recorded location and date, which ordinary voice, SMS and mobile-data tests succeed?", "kind": "measurement", "id": "current-telephony-usability-q02" } ] } ] }, { "id": "accounts-and-remote-features", "name": "Accounts and remote features", "description": "Map account and remote-service requirements for each desired feature.", "findings": [ { "id": "remote-dependency-status", "name": "Remote dependency status", "description": "Track sign-in, synchronisation, application distribution and other remote dependencies individually, including failures whose cause remains uncertain.", "questions": [ { "text": "Which account, endpoint or remote service does each intended workflow require?", "kind": "definition", "id": "remote-dependency-status-q01" }, { "text": "What dated test or provider notice establishes availability, and can observed failures be distinguished from clock, certificate or credential problems?", "kind": "provenance", "id": "remote-dependency-status-q02" } ] } ] } ] }, { "id": "preservation-repair-and-retirement", "name": "Preservation, repair and retirement", "description": "Choose maintenance and end-of-use actions while accounting for legacy software and recoverable data.", "rationale": "Resetting or restoring a Windows Phone may remove applications or access that cannot readily be recreated.", "layers": [ { "id": "data-and-installed-state-preservation", "name": "Data and installed-state preservation", "description": "Determine what can be extracted and what depends on retaining the current installation.", "findings": [ { "id": "pre-reset-preservation", "name": "Pre-reset preservation", "description": "Assess photos, contacts, messages and application data separately, including whether a backup can actually be restored.", "questions": [ { "text": "Which data classes can be exported through currently working local or account-based mechanisms on this release?", "kind": "action", "id": "pre-reset-preservation-q01" }, { "text": "Which installed applications, credentials or data would become unavailable after reset, and what evidence supports any claimed restoration route?", "kind": "boundary", "id": "pre-reset-preservation-q02" } ] } ] }, { "id": "repair-and-recovery-feasibility", "name": "Repair and recovery feasibility", "description": "Evaluate model-specific physical repair, firmware recovery and retirement options.", "findings": [ { "id": "supported-next-action", "name": "Supported next action", "description": "Connect the observed fault to compatible parts, documented recovery resources and a viable post-repair use.", "questions": [ { "text": "What evidence identifies compatible replacement parts or a trustworthy recovery image and tool for this exact handset variant?", "kind": "provenance", "id": "supported-next-action-q01" }, { "text": "Given battery condition, access state and software dependencies, which repair, preservation or retirement action remains feasible?", "kind": "action", "id": "supported-next-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-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "The supplied PHY.OBJ domain suggests a physical object, but the established product name denotes software; confirm whether the registry intended handsets instead.", "This account uses recalled knowledge without consulted sources; exact support dates and surviving service availability require verification.", "Hardware measurements, radio standards and certification requirements belong to specific handset models and cannot be assigned uniformly to Windows Phone." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Windows Phone 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": [ "Windows Phone 7", "Windows Phone 8", "Windows Phone 8.1" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Windows Phone 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": "Microsoft product name and operating-system version", "value_or_pattern": "Windows Phone 7; Windows Phone 8; Windows Phone 8.1", "note": "These identify software generations; handset model numbers identify the physical devices running them." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Windows Phone 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": [ "Provided calling, messaging, contacts and calendar functions on compatible smartphones.", "Supported mobile web browsing, email and downloadable applications.", "Used a Start screen of tiles, including live tiles that could display updated information.", "Supported photography, media playback and location-based applications on compatible hardware." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Windows Phone 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": [ "Discontinued security maintenance leaves unresolved vulnerabilities relevant to continued use.", "Retirement of application distribution and backend services can prevent installation, authentication or synchronization.", "Application compatibility differs across operating-system generations and handset capabilities.", "Mobile-network retirement can impair calling or data service on handsets lacking compatible network support." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Windows Phone 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": [ "Application availability, language support and Microsoft service availability varied by market.", "Handset availability and software-update delivery varied by manufacturer, carrier and region." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Windows Phone 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": "Windows Phone handset", "difference": "A physical smartphone running Windows Phone; Windows Phone itself names its operating-system family." }, { "name": "Windows Mobile", "difference": "An earlier Microsoft mobile operating-system family that preceded Windows Phone." }, { "name": "Windows 10 Mobile", "difference": "The succeeding mobile operating system, branded as part of Windows 10 rather than Windows Phone." }, { "name": "Nokia Lumia", "difference": "A branded device family that included Windows Phone handsets; it is not the operating system." }, { "name": "Android", "difference": "A separate mobile operating-system platform with a different software architecture and application ecosystem." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Windows Phone this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the underlying registry source identify Windows Phone as an operating system, requiring correction of the provisional physical-handset interpretation?", "Should Windows 10 Mobile handsets be included by lineage, linked as a neighbouring kind, or treated differently according to their original shipping platform?", "Which broader smartphone or existing world model should supply shared hardware, battery-safety, radio-compliance and disposal requirements without duplication?", "Which application installation, account, synchronisation and recovery routes remain available for each Windows Phone release, supported by dated primary evidence?", "Which model-specific sources establish radio compatibility, repair constraints and data-export or restoration limits for representative handset variants?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 15, "questions": 23 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "unclassified", "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 Windows Phone, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise a Windows Phone handset, assess its hardware and software state, and determine which uses, repairs and data-preservation actions remain feasible.", "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: Windows Phone 8.1, Windows 10 Mobile, Windows Phone 8.", "3 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 Windows Phone, 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 and material. The registry holds no appearance data, so what a Windows Phone looks like has to come from research." ], "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": [ "Windows Phone 8.1", "Windows 10 Mobile", "Windows Phone 8" ] } ], "standing": "Described in 74 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 3 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 Windows Phone from another, and a Windows Phone 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 Windows Phone, 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 Windows Phone, 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 Windows Phone 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 Windows Phone, 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 Windows Phone, 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 Windows Phone 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 Windows Phone 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 Windows Phone, 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 Windows Phone, 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 Windows Phone 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 Windows Phone from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Windows Phone, 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 Windows Phone, 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 Windows Phone 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 Windows Phone 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 Windows Phone, 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 Windows Phone, 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 Windows Phone 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 Windows Phone is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Windows Phone, 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 Windows Phone, 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 Windows Phone 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 Windows Phone is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Windows Phone, 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 Windows Phone, 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 Windows Phone 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 Windows Phone 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 Windows Phone is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Windows Phone, 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 Windows Phone, 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 Windows Phone 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 Windows Phone 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 Windows Phone, 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 Windows Phone, 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 Windows Phone 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 Windows Phone 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 Windows Phone between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Windows Phone, 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 Windows Phone, 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 Windows Phone 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 Windows Phone, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Windows Phone 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 Windows Phone, 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 Windows Phone, 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 Windows Phone is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "use-and-operation", "name": "Use and operation", "description": "What can be done with a Windows Phone and what it takes to do it.", "rationale": "An agent that can recognise a thing but not act on it has only half a model.", "layers": [ { "id": "intended-use", "name": "Intended use and function", "description": "What a Windows Phone is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Windows Phone performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Windows Phone, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "function-and-purpose-q02", "text": "Who or what asserted this about the use of a Windows Phone, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "function-and-purpose-q03", "text": "What may an agent decide or do once the use of a Windows Phone is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "handling-and-procedure", "name": "Handling and procedure", "description": "The steps, skills and tools involved in using a Windows Phone.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Windows Phone at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Windows Phone, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "procedures-and-skills-q02", "text": "Who or what asserted this about handling a Windows Phone, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "procedures-and-skills-q03", "text": "What may an agent decide or do once handling a Windows Phone is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a Windows Phone 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 Windows Phone and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Windows Phone, 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 Windows Phone, 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 Windows Phone 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 Windows Phone is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Windows Phone, 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 Windows Phone, 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 Windows Phone is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 6, "layers": 13, "findings": 15, "questions": 45 } } } }