{ "model": { "rank": 1987, "code": "thing-q13479982", "model_id": "vr.tr.cryptocurrency", "name": "cryptocurrency", "purpose": "Enable an AI agent to identify a cryptocurrency, assess its ledger, supply, control and transfer conditions, and determine which actions are technically possible and authorised.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q13479982/", "tier": 2, "score": 119, "payload": { "layer": "wikidata", "aliases": [ "digital currency exchanger", "CoinMarketCap", "proof-of-work cryptocurrency", "meme coin", "social token", "altcoin", "stablecoin", "non-fungible token", "Bitchcoin" ], "aliasCount": 9, "merged": 9, "knownIn": 119, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q13479982", "url": "https://www.wikidata.org/wiki/Q13479982", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T09:14:23Z", "providers": [ "Codex" ], "missingProviders": [ "Grok" ], "pass": 2, "cost": { "grok": { "usd": null, "turns": null, "seconds": 14.9, "error": "Error: Internal error: {\n \"message\": \"API error (status 402 Payment Required): Grok Build usage balance exhausted\",\n \"http_status\": 402\n}", "retried": true }, "codex": { "seconds": 78.2, "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: 01a07b24-85ad-7e41-87d7-515caa4ee919\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: cryptocurrency\nRegistry id: vr.tr.cryptocurrency\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (no" } } }, "metaModel": { "id": "THING-Q13479982", "registryId": "vr.tr.cryptocurrency", "name": "cryptocurrency", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q13479982/", "model": { "registry_id": "vr.tr.cryptocurrency", "name": "cryptocurrency", "purpose": "Enable an AI agent to identify a cryptocurrency, assess its ledger, supply, control and transfer conditions, and determine which actions are technically possible and authorised.", "definition": "", "scope_statement": "This model owns the identity and operational state of a cryptocurrency as a fungible digital asset whose issuance, holdings and transfers are governed by cryptographically authenticated ledger rules; it distinguishes the asset from its network, particular holdings, custody arrangements and representations on other networks.", "in_scope": [ "Asset identity, authoritative ledger and continuity across upgrades or forks", "Rules for issuance, distribution, burning and effective supply", "Transfer validity, settlement, fees and dependencies on ledger operation", "Asset-specific administrative powers, restrictions and upgrade mechanisms", "Economic roles, backing or redemption claims, and representation dependencies" ], "out_of_scope": [ "Complete blockchain network architecture and node operations", "Wallet software, private-key storage and individual custody arrangements", "Individual accounts, balances, portfolios and transaction histories", "Exchange operations, trading strategies and investment recommendations", "Issuer organisation management and reserve-asset models", "Non-fungible tokens and conventional bank-account money" ], "distinguishing_features": [ "Identify the asset through its ledger and native-asset identifier or token contract; a matching name or ticker alone does not establish identity.", "Establish whether units are fungible under the asset rules; individually identified assets with materially different rights belong to a neighbouring model.", "Distinguish ledger-recognised units from an exchange balance or custodial receipt that merely promises delivery of those units.", "Determine whether transfer authority is exercised through cryptographically authenticated ledger instructions, rather than solely through updates to a conventional account provider's database.", "Distinguish a native asset from a wrapped or bridged representation by identifying any separate minting, custody, redemption or bridge dependency." ], "characteristics": [ { "name": "Asset locator", "kind": "relation", "unit_or_values": "Ledger or network reference plus native denomination identifier or token contract address", "why_it_matters": "Prevents confusion between assets sharing names, tickers or branding." }, { "name": "Asset implementation", "kind": "category", "unit_or_values": "Native ledger asset | contract-issued token | other ledger-issued asset | unresolved", "why_it_matters": "Identifies which rules and dependencies govern balances and transfers." }, { "name": "Unit precision", "kind": "measurement", "unit_or_values": "Smallest transferable fraction of one named unit, with display conversion", "why_it_matters": "Prevents denomination errors and invalid transfer amounts." }, { "name": "Supply at reference state", "kind": "measurement", "unit_or_values": "Asset units at a specified block or ledger state, with supply definition and exclusions", "why_it_matters": "Makes supply observations reproducible and distinguishes minted, circulating, locked and redeemable quantities." }, { "name": "Issuance authority", "kind": "relation", "unit_or_values": "Protocol rule, contract function or authorised actor able to create units, with conditions", "why_it_matters": "Shows how supply can change and who can influence dilution." }, { "name": "Transfer availability", "kind": "state", "unit_or_values": "Available | restricted | paused | ledger unavailable | unknown, at a stated observation point", "why_it_matters": "Determines whether a proposed transfer can currently proceed." }, { "name": "Settlement criterion", "kind": "category", "unit_or_values": "Protocol finality | confirmation-based policy | external settlement dependency | unresolved, with acceptance rule", "why_it_matters": "Separates transaction inclusion from an acceptable level of reversal risk." }, { "name": "Administrative capabilities", "kind": "relation", "unit_or_values": "Actors or governance mechanisms linked to mint, burn, freeze, seize, pause or upgrade powers; absence requires evidence", "why_it_matters": "Exposes powers that can alter ownership conditions or invalidate operating assumptions." }, { "name": "Backing and redemption dependency", "kind": "relation", "unit_or_values": "Claimed backing, reference asset, obligor, redemption mechanism and supporting evidence, or none established", "why_it_matters": "Distinguishes a value target from an enforceable or executable claim." } ], "affordances": [ "Resolve and verify an asset identifier before accepting a balance, quote or transfer instruction.", "Inspect supply and asset rules at a specified ledger state and identify changes affecting use.", "Evaluate a proposed transfer for amount precision, spend authority, restrictions, fee requirements and settlement conditions.", "Prepare or submit an explicitly authorised transfer when the required signing and execution capabilities are available.", "Assess whether an authorised mint, burn, wrap, unwrap or redemption operation exists and identify its prerequisites.", "Monitor forks, administrative changes, pauses and dependency failures, and flag affected actions for reassessment." ] }, "sources": [], "structure": { "bundles": [ { "id": "asset-identity-and-continuity", "name": "Asset identity and continuity", "description": "Establishes which cryptocurrency is being modelled and how its identity persists or branches.", "rationale": "Names and tickers cannot reliably distinguish original assets, copies, forks and representations.", "layers": [ { "id": "ledger-bound-identity", "name": "Ledger-bound identity", "description": "Connects the asset to the ledger rules that recognise its units.", "findings": [ { "id": "authoritative-asset-locator", "name": "Authoritative asset locator", "description": "Record the network context, native identifier or contract address, denomination and evidence establishing the intended asset.", "questions": [ { "text": "Which ledger and native identifier or contract address uniquely identify this cryptocurrency?", "kind": "definition", "id": "authoritative-asset-locator-q01" }, { "text": "Which independently checkable records connect this identifier to the intended asset rather than a namesake or copy?", "kind": "provenance", "id": "authoritative-asset-locator-q02" } ] } ] }, { "id": "forks-and-representations", "name": "Forks and representations", "description": "Separates continuity claims from distinct assets and dependent representations.", "findings": [ { "id": "continuity-boundary", "name": "Continuity boundary", "description": "Record forks, migrations and representations with explicit reasons for treating them as the same asset or as linked assets.", "questions": [ { "text": "What evidence determines whether a fork or contract migration preserves this asset's identity?", "kind": "boundary", "id": "continuity-boundary-q01" }, { "text": "Which similarly named units are separate bridged, wrapped or custodial claims, and what connects them to this asset?", "kind": "boundary", "id": "continuity-boundary-q02" } ] } ] } ] }, { "id": "units-and-supply", "name": "Units and supply", "description": "Captures denomination, supply accounting and mechanisms that create or remove units.", "rationale": "An agent needs reproducible quantities and explicit supply rules to avoid amount errors and unsupported scarcity assumptions.", "layers": [ { "id": "denomination-and-accounting", "name": "Denomination and accounting", "description": "Defines how ledger quantities become asset amounts and how supply is counted.", "findings": [ { "id": "reproducible-asset-quantities", "name": "Reproducible asset quantities", "description": "Record base-unit conversion and supply measures tied to a ledger state, including treatment of locked or inaccessible units.", "questions": [ { "text": "What is the smallest transferable unit, and how does it convert to the displayed denomination?", "kind": "measurement", "id": "reproducible-asset-quantities-q01" }, { "text": "At which ledger state was each supply figure measured, and which units were included or excluded?", "kind": "measurement", "id": "reproducible-asset-quantities-q02" } ] } ] }, { "id": "issuance-and-removal", "name": "Issuance and removal", "description": "Identifies mechanisms that change supply and the conditions governing them.", "findings": [ { "id": "supply-change-rules", "name": "Supply change rules", "description": "Record minting, rewards, burning or rebasing mechanisms, including any limits and powers to alter those limits.", "questions": [ { "text": "Which executable rules or authorised actors can increase or decrease supply, and under what conditions?", "kind": "definition", "id": "supply-change-rules-q01" }, { "text": "Can a stated supply cap or issuance schedule be changed, and through which mechanism?", "kind": "boundary", "id": "supply-change-rules-q02" } ] } ] } ] }, { "id": "transfer-and-settlement", "name": "Transfer and settlement", "description": "Captures the requirements for moving units and judging completion.", "rationale": "A visible balance does not by itself establish spendability, execution feasibility or acceptable settlement.", "layers": [ { "id": "transfer-execution", "name": "Transfer execution", "description": "Defines asset-specific preconditions and effects of a transfer.", "findings": [ { "id": "valid-and-authorised-transfer", "name": "Valid and authorised transfer", "description": "Record required spend authority, address constraints, available units, fees and transfer behaviour.", "questions": [ { "text": "What signing authority, spendable amount and recipient conditions must an authorised transfer satisfy?", "kind": "action", "id": "valid-and-authorised-transfer-q01" }, { "text": "Which asset pays execution fees, and can transfer taxes, deductions or asset rules change the recipient's amount?", "kind": "measurement", "id": "valid-and-authorised-transfer-q02" } ] } ] }, { "id": "settlement-and-availability", "name": "Settlement and availability", "description": "Connects transaction status to ledger operation and reversal conditions.", "findings": [ { "id": "acceptance-of-settlement", "name": "Acceptance of settlement", "description": "Record inclusion evidence, finality conditions and operational interruptions relevant to accepting a payment.", "questions": [ { "text": "What ledger evidence and acceptance policy distinguish a pending, included and sufficiently settled transfer?", "kind": "definition", "id": "acceptance-of-settlement-q01" }, { "text": "Which observed halt, reorganisation or settlement-dependency condition should delay acceptance or further transfer?", "kind": "action", "id": "acceptance-of-settlement-q02" } ] } ] } ] }, { "id": "control-and-rule-changes", "name": "Control and rule changes", "description": "Identifies powers over asset behaviour and how those powers can be exercised or changed.", "rationale": "Cryptographic ownership can coexist with administrative restrictions and mutable rules that affect permitted actions.", "layers": [ { "id": "privileged-asset-controls", "name": "Privileged asset controls", "description": "Captures exceptional powers over balances, transfers and asset operation.", "findings": [ { "id": "intervention-powers", "name": "Intervention powers", "description": "Record evidenced freeze, pause, seizure, forced-transfer and comparable capabilities, together with their controllers.", "questions": [ { "text": "Which actors or mechanisms can restrict transfers, alter balances or move units without a holder's signature?", "kind": "boundary", "id": "intervention-powers-q01" }, { "text": "What deployed code, ledger configuration or execution history establishes each capability and its current controller?", "kind": "provenance", "id": "intervention-powers-q02" } ] } ] }, { "id": "upgrades-and-governance", "name": "Upgrades and governance", "description": "Describes how asset rules change and when new rules become effective.", "findings": [ { "id": "rule-change-authority", "name": "Rule change authority", "description": "Record proposal, approval, execution and adoption requirements for changes that affect the asset.", "questions": [ { "text": "How can asset rules be changed, and which approvals, delays or network adoption steps are required?", "kind": "definition", "id": "rule-change-authority-q01" }, { "text": "Which pending or activated changes require an agent to recheck supply, transfer or redemption assumptions before acting?", "kind": "action", "id": "rule-change-authority-q02" } ] } ] } ] }, { "id": "economic-role-and-dependencies", "name": "Economic role and dependencies", "description": "Distinguishes protocol uses, external claims and practical conversion conditions.", "rationale": "A cryptocurrency's usability depends on what its units enable and on any mechanisms needed to exchange or redeem them.", "layers": [ { "id": "utility-and-redemption", "name": "Utility and redemption", "description": "Separates executable asset functions from promised rights and value targets.", "findings": [ { "id": "unit-functions-and-claims", "name": "Unit functions and claims", "description": "Record fee payment, staking, governance or other supported functions, and any backing or redemption claim with its conditions.", "questions": [ { "text": "Which actions or rights do units enable, and which are enforced by ledger rules versus an external party?", "kind": "definition", "id": "unit-functions-and-claims-q01" }, { "text": "If backing or redemption is claimed, what evidence identifies the obligor, eligible redeemers and delivery conditions?", "kind": "provenance", "id": "unit-functions-and-claims-q02" } ] } ] }, { "id": "conversion-and-dependency-exposure", "name": "Conversion and dependency exposure", "description": "Captures observable exchange feasibility and dependencies that can impair use or value claims.", "findings": [ { "id": "usable-conversion-paths", "name": "Usable conversion paths", "description": "Record available exchange or redemption routes, size-dependent execution conditions and critical dependencies without treating quoted prices as guaranteed proceeds.", "questions": [ { "text": "For a specified amount and observation time, what route, liquidity, fees and restrictions determine feasible conversion proceeds?", "kind": "measurement", "id": "usable-conversion-paths-q01" }, { "text": "Which bridge, custodian, reserve, oracle or market dependency failures would require suspending a proposed conversion or redemption?", "kind": "action", "id": "usable-conversion-paths-q02" } ] } ] } ] } ] }, "openQuestions": [ "With no registry definition recorded, does cryptocurrency include all fungible ledger tokens, including stablecoins, tokenised claims and governance tokens, or a narrower subset?", "How should the registry's PHY / PHY.OBJ placement relate to the distinction between an asset type, its ledger representation and a particular holding?", "What identity policy should determine continuity across contentious forks, contract migrations and multiple issuer-designated deployments?", "Which supply definitions and evidence thresholds should be required when circulating, inaccessible or economically redeemable quantities cannot be directly established?", "Which jurisdictional and holder-specific rights should be linked from neighbouring models when assessing redemption eligibility and authorised use?" ], "statistics": { "bundles": 5, "layers": 10, "findings": 10, "questions": 20 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "device, machine or tool", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a cryptocurrency, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to identify a cryptocurrency, assess its ledger, supply, control and transfer conditions, and determine which actions are technically possible and authorised.", "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: digital currency exchanger, CoinMarketCap, proof-of-work cryptocurrency, meme coin, social token, altcoin, stablecoin, non-fungible token, Bitchcoin.", "9 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 119 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 cryptocurrency, and on what evidence are they told apart?" ], "whatItIsMadeOf": "matter you can touch", "physicalCharacter": [ "Mobility varies between examples.", "Does nothing on its own; everything it does, something else did to it.", "These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing." ], "whatCanBeDoneWithIt": [ "observe it, measure it, record its state" ], "howItIsRecognised": [ "Recognised by form, by the arrangement of its controls, and by markings - a plate, a model number, a certification mark. Form alone rarely separates two models that do very different things." ], "relatedModels": [ { "relation": "covers", "note": "Finer kinds folded into this entry because telling them apart needs a task that asks for it. Each is a model waiting to be split out when one does.", "targets": [ "digital currency exchanger", "CoinMarketCap", "proof-of-work cryptocurrency", "meme coin", "social token", "altcoin", "stablecoin", "non-fungible token", "Bitchcoin" ] } ], "standing": "Described in 119 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 9 finer distinctions are held inside this entry as names rather than as separate models.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one cryptocurrency from another, and a cryptocurrency 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 cryptocurrency, 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 cryptocurrency, 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 cryptocurrency 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 cryptocurrency, 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 cryptocurrency, 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 cryptocurrency 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 cryptocurrency 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 cryptocurrency, 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 cryptocurrency, 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 cryptocurrency 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 cryptocurrency from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a cryptocurrency, 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 cryptocurrency, 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 cryptocurrency 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 cryptocurrency 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 cryptocurrency, 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 cryptocurrency, 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 cryptocurrency 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 cryptocurrency is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a cryptocurrency, 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 cryptocurrency, 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 cryptocurrency 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 cryptocurrency is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a cryptocurrency, 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 cryptocurrency, 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 cryptocurrency 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 cryptocurrency 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 cryptocurrency is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a cryptocurrency, 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 cryptocurrency, 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 cryptocurrency 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 cryptocurrency 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 cryptocurrency, 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 cryptocurrency, 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 cryptocurrency 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 cryptocurrency 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 cryptocurrency between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a cryptocurrency, 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 cryptocurrency, 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 cryptocurrency 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 cryptocurrency, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a cryptocurrency 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 cryptocurrency, 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 cryptocurrency, 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 cryptocurrency is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "function-and-principle", "name": "Function and operating principle", "description": "What cryptocurrency is for and how it achieves it.", "rationale": "Two devices with the same name can work on different principles, and the principle is what predicts failure and constrains use.", "layers": [ { "id": "intended-function", "name": "Intended function", "description": "The job it does, and the jobs it is used for anyway.", "findings": [ { "id": "function-record", "name": "Function, principle and variants", "description": "What it does, how, and which variants do it differently.", "questions": [ { "id": "function-record-q01", "text": "What function does cryptocurrency perform, on what operating principle, and which variants differ in that principle?", "kind": "definition" }, { "id": "function-record-q02", "text": "What use falls outside the intended function but happens in practice?", "kind": "boundary" } ] } ] }, { "id": "capacity-and-rating", "name": "Capacity and rating", "description": "The numbers that say what it can do and where it stops.", "findings": [ { "id": "ratings", "name": "Ratings and their conditions", "description": "Rated capacity, power, throughput and the conditions each assumes.", "questions": [ { "id": "ratings-q01", "text": "What ratings characterise cryptocurrency, in what units, and under what stated conditions?", "kind": "measurement" }, { "id": "ratings-q02", "text": "What happens beyond the rating - degradation, refusal, damage - and how is that detected?", "kind": "action" } ] } ] } ] }, { "id": "operation-and-state", "name": "Operation, controls and state", "description": "How cryptocurrency is operated and what state it is in right now.", "rationale": "An agent acting on a device needs its current state and the controls that change it, not just its specification.", "layers": [ { "id": "controls-and-modes", "name": "Controls and modes", "description": "What can be set, what that changes, and what is interlocked.", "findings": [ { "id": "control-surface", "name": "Control surface and interlocks", "description": "The settings available and the conditions that block them.", "questions": [ { "id": "control-surface-q01", "text": "What controls and modes does cryptocurrency have, and what does each change?", "kind": "definition" }, { "id": "control-surface-q02", "text": "Which actions are interlocked or forbidden in which state, and what must be true before acting?", "kind": "action" } ] } ] }, { "id": "condition-and-maintenance", "name": "Condition and maintenance", "description": "Wear, service intervals, consumables and the line between working and broken.", "findings": [ { "id": "service-record", "name": "Condition, service and consumables", "description": "What is consumed, what is serviced, and how condition is judged.", "questions": [ { "id": "service-record-q01", "text": "What consumables and service does cryptocurrency need, at what interval, and on whose authority?", "kind": "measurement" }, { "id": "service-record-q02", "text": "What evidence separates a unit that is working from one that is out of service?", "kind": "boundary" } ] } ] } ] }, { "id": "kind-model-unit", "name": "Kind, model and unit", "description": "Whether a claim about cryptocurrency is about the kind, a product line, or one physical unit.", "rationale": "This is the boundary most often got wrong for made things, and getting it wrong mixes a catalogue entry with the machine in the yard.", "layers": [ { "id": "level-of-reference", "name": "Level of reference", "description": "The three levels and what belongs at each.", "findings": [ { "id": "level-rules", "name": "What belongs to kind, model and unit", "description": "Which properties are shared by all of them and which are not.", "questions": [ { "id": "level-rules-q01", "text": "Which facts about cryptocurrency hold for every one of them, which for a model, and which only for one unit?", "kind": "boundary" }, { "id": "level-rules-q02", "text": "What identifies an individual unit, and what should an agent do when it has only the kind?", "kind": "action" } ] } ] }, { "id": "standards-and-conformity", "name": "Standards and conformity", "description": "The standards a working example must meet and who attests it.", "findings": [ { "id": "conformity", "name": "Standards, marks and attestation", "description": "Which standard applies, who certifies, and what the mark means.", "questions": [ { "id": "conformity-q01", "text": "Which standards govern cryptocurrency, issued by whom, and what does conformity actually assert?", "kind": "provenance" }, { "id": "conformity-q02", "text": "What may an agent conclude from a certification mark, and what may it not?", "kind": "boundary" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a cryptocurrency 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 cryptocurrency and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a cryptocurrency, 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 cryptocurrency, 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 cryptocurrency 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 cryptocurrency is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a cryptocurrency, 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 cryptocurrency, 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 cryptocurrency is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 8, "layers": 17, "findings": 19, "questions": 51 } } } }