{ "model": { "rank": 1363, "code": "thing-q131723", "model_id": "vr.tr.bitcoin", "name": "Bitcoin", "purpose": "Enable an AI agent to recognise Bitcoin, assess the state and spendability of bitcoin holdings and transactions, and determine which actions are technically possible and authorised.", "family": "Thing Registry", "category": "Activities and processes", "status": "research-draft", "kind": "thing", "plane": "ACT", "domain": "ACT.ACT", "industry": "", "version": "", "url": "/models/thing/q131723/", "tier": 2, "score": 152, "payload": { "layer": "wikidata", "aliases": [ "Kodak KashMiner" ], "aliasCount": 1, "merged": 1, "knownIn": 152, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q131723", "url": "https://www.wikidata.org/wiki/Q131723", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T11:22:18Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 31.9, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a07b99-b774-7c80-8fdb-caada0a4a5c5\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Bitcoin\nSense to describe: (none recorded)\nDomain code: ACT.ACT\nAlso known as: (none)\n\n\nContext for this batch of 210 things:\n# Batch 001: 1001 register", "usd": 0, "recall": true }, "codex": { "seconds": 72.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: 01a07b99-b761-7ee0-bbaa-c3155264f066\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Bitcoin\nRegistry id: vr.tr.bitcoin\nPlane / domain: ACT / ACT.ACT\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nContext " } } }, "metaModel": { "id": "THING-Q131723", "registryId": "vr.tr.bitcoin", "name": "Bitcoin", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "ACT.ACT" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q131723/", "model": { "registry_id": "vr.tr.bitcoin", "name": "Bitcoin", "purpose": "Enable an AI agent to recognise Bitcoin, assess the state and spendability of bitcoin holdings and transactions, and determine which actions are technically possible and authorised.", "definition": "Bitcoin is a decentralized peer-to-peer monetary system whose native asset, bitcoin, is transferred through digitally signed transactions and whose shared transaction history is maintained by nodes enforcing consensus rules and miners performing proof of work.", "scope_statement": "This model owns vr.tr.bitcoin as the Bitcoin mainnet monetary network, its native asset BTC, and the protocol-governed activities that create, validate and transfer that asset, distinguishing these senses within one registry entry.", "in_scope": [ "Bitcoin mainnet identity, consensus rules and competing interpretations of Bitcoin's monetary role", "BTC denomination, issuance and unspent transaction outputs", "Transaction construction, validation, propagation and confirmation", "Key-based spending control, custody arrangements and action authority", "Proof-of-work chain selection, reorganisations and protocol change" ], "out_of_scope": [ "Generic blockchain and cryptocurrency concepts beyond what distinguishes Bitcoin", "Separate fork networks and their native assets", "Wrapped BTC, exchange account credits and investment products as independently issued claims", "Lightning channel operation and other overlay protocols, except their Bitcoin settlement dependencies", "Mining hardware engineering, electricity infrastructure and environmental accounting", "Personal investment suitability, portfolio allocation and jurisdiction-specific tax determinations" ], "distinguishing_features": [ "Identify Bitcoin mainnet through its genesis and applicable consensus rules; a BTC ticker, address appearance or marketing name alone is insufficient.", "Distinguish native bitcoin represented by mainnet unspent transaction outputs from a custodian's balance or a token issued on another network.", "Test spending through transaction inputs, output amounts and script conditions rather than assuming a mutable account balance.", "Assess chain selection using accumulated proof of work among valid chains, rather than block count alone or an institution's approval.", "Distinguish Bitcoin's subsidy schedule from discretionary issuance, while recording the rule set against which issuance is checked." ], "characteristics": [ { "name": "Referent sense", "kind": "category", "unit_or_values": "network | native asset | protocol | monetary practice", "why_it_matters": "Prevents statements about BTC holdings from being confused with statements about software, infrastructure or social adoption." }, { "name": "Network identity", "kind": "relation", "unit_or_values": "Genesis block reference, network designation and consensus-rule context", "why_it_matters": "Separates Bitcoin mainnet from test networks and independently operating forks." }, { "name": "Amount", "kind": "measurement", "unit_or_values": "Integer satoshis; 100,000,000 satoshis per BTC", "why_it_matters": "Supports exact accounting and avoids floating-point ambiguity." }, { "name": "Observed chain tip", "kind": "state", "unit_or_values": "Block hash, height, accumulated chainwork, observation time and observing node", "why_it_matters": "Makes confirmation and spendability assessments relative to an explicit chain view." }, { "name": "Output spendability", "kind": "state", "unit_or_values": "Unspent status, script requirements, maturity or timelock conditions and available signing capability", "why_it_matters": "An apparent holding may not be spendable by the agent or at the present chain state." }, { "name": "Transaction status", "kind": "state", "unit_or_values": "Constructed | partially signed | signed | observed unconfirmed | confirmed | conflicted; qualified by observer and time", "why_it_matters": "Distinguishes preparation, local network observations and inclusion in the selected chain." }, { "name": "Confirmation depth", "kind": "measurement", "unit_or_values": "Blocks, relative to a named chain tip; zero if unconfirmed", "why_it_matters": "Supports risk-based settlement decisions without implying irreversible finality." }, { "name": "Transaction fee rate", "kind": "measurement", "unit_or_values": "Satoshis per virtual byte", "why_it_matters": "Relates transaction cost to block-space demand and inclusion expectations." }, { "name": "Control and authority", "kind": "relation", "unit_or_values": "Output or custody claim linked to signers, spending policy and authorising principal", "why_it_matters": "Separates technical ability to sign from permission to transfer value." }, { "name": "Monetary interpretation", "kind": "category", "unit_or_values": "Attributed interpretations such as payment medium, scarce digital asset, speculative asset or monetary alternative", "why_it_matters": "Keeps contested economic descriptions attributable and separate from protocol-observable properties." } ], "affordances": [ "Verify a purported Bitcoin network, output or transaction against an explicit mainnet chain view.", "Calculate amounts, fees and spendability from identified outputs and their spending conditions.", "Prepare and inspect a transaction for recipient, change, fee, privacy and authorisation requirements.", "Coordinate authorised signing and broadcast while keeping secret key material outside the model.", "Monitor confirmation depth, conflicts and reorganisations against a stated acceptance policy.", "Compare attributed monetary claims with specified evidence and operational measures." ] }, "sources": [], "structure": { "bundles": [ { "id": "bitcoin-identity-and-meaning", "name": "Bitcoin identity and meaning", "description": "Distinguishes the network, native asset and contested monetary interpretations covered by this entry.", "rationale": "Bitcoin names several connected referents, and technical identity does not settle its economic classification.", "layers": [ { "id": "mainnet-and-asset-boundary", "name": "Mainnet and asset boundary", "description": "Establishes whether the subject is native Bitcoin or a neighbouring network or claim.", "findings": [ { "id": "native-bitcoin-identification", "name": "Native bitcoin identification", "description": "Record evidence connecting the subject to Bitcoin mainnet and distinguish native outputs from representations or redemption claims.", "questions": [ { "text": "Which genesis reference and consensus context identify the network being examined?", "kind": "definition", "id": "native-bitcoin-identification-q01" }, { "text": "Does the purported holding identify mainnet outputs or a claim against another issuer or custodian?", "kind": "boundary", "id": "native-bitcoin-identification-q02" } ] } ] }, { "id": "monetary-interpretations", "name": "Monetary interpretations", "description": "Records competing accounts of Bitcoin's purpose and use without treating one account as settled.", "findings": [ { "id": "attributed-economic-claims", "name": "Attributed economic claims", "description": "Associate descriptions such as money, store of value or speculative asset with their proponents, definitions and evidence.", "questions": [ { "text": "Who advances this interpretation of Bitcoin, and where is their definition stated?", "kind": "provenance", "id": "attributed-economic-claims-q01" }, { "text": "Which observable measures would support or challenge that interpretation over a specified period?", "kind": "measurement", "id": "attributed-economic-claims-q02" } ] } ] } ] }, { "id": "bitcoin-amounts-and-issuance", "name": "Bitcoin amounts and issuance", "description": "Models denomination, output-based holdings and rule-governed creation of bitcoin.", "rationale": "An agent must distinguish exact amounts, spendable outputs and issuance claims before accounting for BTC.", "layers": [ { "id": "utxo-holdings", "name": "UTXO holdings", "description": "Represents holdings through identified unspent transaction outputs and explicit aggregation assumptions.", "findings": [ { "id": "output-based-balance", "name": "Output-based balance", "description": "Record output references, satoshi amounts and the chain view under which they are unspent.", "questions": [ { "text": "Which transaction identifiers and output indices contribute to the stated BTC amount?", "kind": "measurement", "id": "output-based-balance-q01" }, { "text": "Which outputs are excluded because they are spent, immature, locked or outside the relevant control policy?", "kind": "boundary", "id": "output-based-balance-q02" } ] } ] }, { "id": "subsidy-and-supply", "name": "Subsidy and supply", "description": "Separates permitted issuance, observed issuance and estimates of economically available supply.", "findings": [ { "id": "supply-accounting-basis", "name": "Supply accounting basis", "description": "Record the height and rules used for subsidy calculations, distinguishing newly issued value from transaction fees and uncertain loss estimates.", "questions": [ { "text": "What subsidy is permitted at the assessed height, and how is it distinguished from fees in the coinbase transaction?", "kind": "measurement", "id": "supply-accounting-basis-q01" }, { "text": "Does the supply claim refer to permitted issuance, actual issuance, unspent value or an estimate excluding inaccessible coins?", "kind": "definition", "id": "supply-accounting-basis-q02" } ] } ] } ] }, { "id": "bitcoin-transactions-and-settlement", "name": "Bitcoin transactions and settlement", "description": "Follows a proposed spend through construction, network observation and risk-based acceptance.", "rationale": "A signed transaction, mempool observation and confirmed payment support different decisions.", "layers": [ { "id": "transaction-construction", "name": "Transaction construction", "description": "Connects selected inputs to intended recipients, change and fee requirements.", "findings": [ { "id": "spend-intent-and-fee", "name": "Spend intent and fee", "description": "Record how a proposed transaction implements the authorised payment and accounts for every input amount.", "questions": [ { "text": "Which outputs pay the intended recipients, which return change, and how were their scripts verified?", "kind": "action", "id": "spend-intent-and-fee-q01" }, { "text": "What total fee and fee rate follow from the input amounts, output amounts and transaction virtual size?", "kind": "measurement", "id": "spend-intent-and-fee-q02" } ] } ] }, { "id": "confirmation-and-conflict", "name": "Confirmation and conflict", "description": "Tracks observer-dependent propagation, chain inclusion and conflicting spends.", "findings": [ { "id": "payment-acceptance-state", "name": "Payment acceptance state", "description": "Record inclusion evidence and the acceptance policy, preserving uncertainty from conflicts and possible reorganisations.", "questions": [ { "text": "Which node observed the transaction, and what inclusion block and confirmation depth does its current chain view establish?", "kind": "measurement", "id": "payment-acceptance-state-q01" }, { "text": "What acceptance threshold and response to replacement, conflicting spends or reorganisation apply to this payment?", "kind": "action", "id": "payment-acceptance-state-q02" } ] } ] } ] }, { "id": "bitcoin-control-and-custody", "name": "Bitcoin control and custody", "description": "Separates script-level spending capability, custody claims and authority to act.", "rationale": "Possession of an address or a displayed balance does not establish either spending capability or permission.", "layers": [ { "id": "script-and-signing-control", "name": "Script and signing control", "description": "Describes the evidence and participants required to satisfy an output's spending conditions.", "findings": [ { "id": "satisfiable-spending-policy", "name": "Satisfiable spending policy", "description": "Record required signatures, script paths and timing conditions through non-secret references.", "questions": [ { "text": "Which signatures, script conditions and timelocks must be satisfied to spend these outputs?", "kind": "definition", "id": "satisfiable-spending-policy-q01" }, { "text": "Which authorised signing devices or participants can satisfy those conditions, and what evidence establishes their availability?", "kind": "action", "id": "satisfiable-spending-policy-q02" } ] } ] }, { "id": "custody-and-authorisation", "name": "Custody and authorisation", "description": "Distinguishes direct control from intermediary obligations and specifies who may approve a spend.", "findings": [ { "id": "holding-and-action-authority", "name": "Holding and action authority", "description": "Record the custody arrangement, withdrawal dependencies and explicit limits on agent actions.", "questions": [ { "text": "Is the balance directly controlled through Bitcoin spending conditions or dependent on a custodian honouring a withdrawal request?", "kind": "boundary", "id": "holding-and-action-authority-q01" }, { "text": "Who may authorise signing or withdrawal, and what recipient, amount and fee limits constrain the agent?", "kind": "action", "id": "holding-and-action-authority-q02" } ] } ] } ] }, { "id": "bitcoin-consensus-and-change", "name": "Bitcoin consensus and change", "description": "Models chain validity, proof-of-work selection and the evidence needed to describe protocol changes.", "rationale": "Bitcoin state depends on validated chain history and adopted rules, while proposals and stakeholder preferences require separate treatment.", "layers": [ { "id": "validation-and-chain-selection", "name": "Validation and chain selection", "description": "Establishes the validation basis for an observed chain and its selected tip.", "findings": [ { "id": "validated-chain-view", "name": "Validated chain view", "description": "Record node software, validation assumptions and chainwork evidence supporting state assessments.", "questions": [ { "text": "Which node implementation, version and validation assumptions produced this chain view?", "kind": "provenance", "id": "validated-chain-view-q01" }, { "text": "What evidence supports selection of this tip by accumulated work among chains valid under the node's rules?", "kind": "measurement", "id": "validated-chain-view-q02" } ] } ] }, { "id": "protocol-evolution", "name": "Protocol evolution", "description": "Distinguishes proposals, implementation behaviour, activation conditions and actual enforcement.", "findings": [ { "id": "rule-change-status", "name": "Rule change status", "description": "Record the specific change and evidence for its status without equating publication, signalling or software release with activation.", "questions": [ { "text": "Which proposal and implementation sources specify the change and its activation conditions?", "kind": "provenance", "id": "rule-change-status-q01" }, { "text": "Is the assessed behaviour a consensus rule, local relay or mining policy, wallet convention or separate network rule?", "kind": "boundary", "id": "rule-change-status-q02" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This description covers both the Bitcoin system and its native asset because no narrower sense was supplied; the ACT.ACT classification should be reviewed.", "These are recalled facts, not findings checked against sources; current legal status and operational statistics require research.", "BIPs are community specifications, not rules issued by a central regulator; claims that bitcoin is money, digital gold or a reliable store of value remain contested." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Bitcoin 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": "Asset ticker", "value_or_pattern": "BTC", "note": "Widely used for bitcoin; a ticker alone does not identify a blockchain or distinguish native bitcoin from wrapped representations." }, { "scheme": "Bitcoin transaction identifier", "value_or_pattern": "txid: 64 hexadecimal characters", "note": "Identifies a transaction; witness transactions also have a distinct witness-inclusive identifier, wtxid." }, { "scheme": "Bitcoin mainnet payment address", "value_or_pattern": "Common prefixes: 1, 3, bc1q, bc1p", "note": "Prefixes distinguish address encodings and spending constructions; an address is not a personal identity or necessarily a persistent account." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Bitcoin 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": [ "BIP 32, Hierarchical Deterministic Wallets: a specification in the community-maintained Bitcoin Improvement Proposals process.", "BIP 141, Segregated Witness: specifies witness-related consensus rules through the Bitcoin Improvement Proposals process.", "BIP 173 and BIP 350: specify Bech32 and Bech32m address encodings through the Bitcoin Improvement Proposals process.", "BIP 340, BIP 341 and BIP 342: specify Schnorr signatures, Taproot and Tapscript through the Bitcoin Improvement Proposals process." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of Bitcoin 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": [ "Transferring value without a central transaction processor.", "Holding an asset for investment, speculation or a proposed store of value.", "Paying participating merchants and individuals.", "Transferring value across borders, sometimes with conversion through exchanges.", "Providing the underlying asset and settlement mechanism for Lightning payment channels." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Bitcoin 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": "Target average interval between blocks", "typical_range": "Approximately 10; individual intervals vary widely", "unit": "minutes" }, { "quantity": "Native accounting subdivision", "typical_range": "100000000 satoshis per bitcoin", "unit": "satoshi/BTC" }, { "quantity": "Maximum scheduled issuance under existing consensus rules", "typical_range": "Approximately 21000000", "unit": "BTC" }, { "quantity": "Maximum block weight", "typical_range": "4000000", "unit": "weight units" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Bitcoin 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": [ "Lost private keys or recovery material can make funds permanently inaccessible; stolen keys can enable unauthorized spending.", "Price volatility can produce substantial losses relative to goods or national currencies.", "Custodians and exchanges can fail, freeze withdrawals or lose customer funds.", "Congestion can raise transaction fees and delay confirmation; reorganizations can reverse recently confirmed transactions.", "Transactions are publicly traceable, while mistaken or fraudulent payments generally lack a built-in reversal mechanism." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Bitcoin 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": [ "Legal treatment, taxation and obligations placed on service providers vary by jurisdiction and require current verification.", "Access to exchanges, banking connections and merchant acceptance varies geographically.", "Mining location depends partly on electricity availability, cost, infrastructure and local policy." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Bitcoin 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": "Cryptocurrency", "difference": "Cryptocurrency is a broader category; Bitcoin is one particular system and native asset." }, { "name": "Blockchain", "difference": "A blockchain is a data structure and ledger approach; Bitcoin combines one with a monetary asset, network and consensus rules." }, { "name": "Bitcoin Cash", "difference": "Bitcoin Cash is a separate network and asset that split from Bitcoin in 2017 and follows different consensus rules." }, { "name": "Lightning Network", "difference": "Lightning enables payments through channels anchored to Bitcoin; its payments are not each recorded as separate Bitcoin blockchain transactions." }, { "name": "Wrapped bitcoin", "difference": "Wrapped representations circulate on other systems and introduce additional custody or bridging assumptions; they are not native Bitcoin outputs." }, { "name": "Bitcoin Core", "difference": "Bitcoin Core is a software implementation used to participate in Bitcoin, rather than the network or asset itself." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Bitcoin this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which existing Vercy world model, if any, already owns Bitcoin or part of this scope and should supply the canonical publication?", "Which primary protocol references and implementation versions should anchor the researched model at publication time?", "How should network-identity disputes and competing monetary definitions be attributed without turning stakeholder claims into settled classifications?", "Which payment contexts require distinct confirmation, conflict and reorganisation response policies?", "What evidence is sufficient to distinguish demonstrably unspendable bitcoin from holdings merely presumed lost or inactive?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 28 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "abstract concept", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a Bitcoin, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise Bitcoin, assess the state and spendability of bitcoin holdings and transactions, and determine which actions are technically possible and authorised.", "characteristics": { "substance": "activity", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: Kodak KashMiner.", "1 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 152 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 Bitcoin, and on what evidence are they told apart?" ], "whatItIsMadeOf": "something that happens over time", "physicalCharacter": [ "Does nothing on its own; everything it does, something else did to it.", "These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing." ], "whatCanBeDoneWithIt": [ "observe it, measure it, record its state" ], "howItIsRecognised": [ "Nothing to see. What is recognised is an instance of it, and which instances count is exactly what is argued about." ], "relatedModels": [ { "relation": "covers", "note": "Finer kinds folded into this entry because telling them apart needs a task that asks for it. Each is a model waiting to be split out when one does.", "targets": [ "Kodak KashMiner" ] } ], "standing": "Described in 152 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 1 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 Bitcoin from another, and a Bitcoin 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 Bitcoin, 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 Bitcoin, 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 Bitcoin 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 Bitcoin, 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 Bitcoin, 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 Bitcoin 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 Bitcoin 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 Bitcoin, 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 Bitcoin, 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 Bitcoin 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 Bitcoin from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Bitcoin, 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 Bitcoin, 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 Bitcoin 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 Bitcoin 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 Bitcoin between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Bitcoin, 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 Bitcoin, 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 Bitcoin 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 Bitcoin, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Bitcoin 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 Bitcoin, 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 Bitcoin, 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 Bitcoin is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "process-and-outcome", "name": "Process, inputs and outcome", "description": "How a Bitcoin proceeds, what it needs and what it leaves behind.", "rationale": "An activity is known by its steps and its results, and both have to be recordable while it is still running.", "layers": [ { "id": "steps-and-sequence", "name": "Steps and sequence", "description": "The steps of a Bitcoin, their order and what may run in parallel.", "findings": [ { "id": "steps-and-preconditions", "name": "Steps, preconditions and completion", "description": "What has to be true before each step of a Bitcoin and what marks it done.", "questions": [ { "id": "steps-and-preconditions-q01", "text": "What identifies and describes a step of a Bitcoin, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "steps-and-preconditions-q02", "text": "Who or what asserted this about a step of a Bitcoin, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "steps-and-preconditions-q03", "text": "What may an agent decide or do once a step of a Bitcoin is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "inputs-and-results", "name": "Inputs, resources and results", "description": "What a Bitcoin consumes and what it produces.", "findings": [ { "id": "inputs-and-outputs", "name": "Inputs, outputs and side effects", "description": "The resources a Bitcoin takes and the results it leaves, wanted or not.", "questions": [ { "id": "inputs-and-outputs-q01", "text": "What identifies and describes the inputs and results of a Bitcoin, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "inputs-and-outputs-q02", "text": "Who or what asserted this about the inputs and results of a Bitcoin, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "inputs-and-outputs-q03", "text": "What may an agent decide or do once the inputs and results of a Bitcoin is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "definitions-in-contest", "name": "Definitions and who holds them", "description": "What Bitcoin is taken to mean, and by whom.", "rationale": "When a field disagrees about a concept, the disagreement is the content. A model that picks one definition silently destroys the information.", "layers": [ { "id": "competing-definitions", "name": "Competing definitions", "description": "The main readings and the traditions behind them.", "findings": [ { "id": "definition-map", "name": "Definitions and their holders", "description": "Each definition with the school or body that holds it.", "questions": [ { "id": "definition-map-q01", "text": "Which definitions of Bitcoin are in use, and which tradition or body holds each?", "kind": "definition" }, { "id": "definition-map-q02", "text": "What turns on the difference between them in practice?", "kind": "boundary" } ] } ] }, { "id": "operationalisation", "name": "Operationalisation", "description": "How it is measured or applied when it has to be.", "findings": [ { "id": "operational-record", "name": "Measures and proxies", "description": "Instruments and indicators used to stand in for it.", "questions": [ { "id": "operational-record-q01", "text": "How is Bitcoin operationalised or measured in practice, and by what instrument?", "kind": "measurement" }, { "id": "operational-record-q02", "text": "What does that operationalisation leave out, and when does that matter?", "kind": "boundary" } ] } ] } ] }, { "id": "instances-and-use", "name": "Instances, use and consequence", "description": "What counts as an instance of Bitcoin and what follows from calling something that.", "rationale": "Applying a concept is an act with consequences, so a model must say what the label licenses and what it does not.", "layers": [ { "id": "instances", "name": "What counts as an instance", "description": "Clear cases, borderline cases and non-cases.", "findings": [ { "id": "instance-tests", "name": "Tests for an instance", "description": "What would settle whether something falls under it.", "questions": [ { "id": "instance-tests-q01", "text": "What would settle whether something is an instance of Bitcoin?", "kind": "boundary" }, { "id": "instance-tests-q02", "text": "Which borderline cases are argued about, and on what grounds?", "kind": "definition" } ] } ] }, { "id": "consequence", "name": "Consequence of application", "description": "Rights, duties or decisions that follow from the label.", "findings": [ { "id": "consequence-record", "name": "What the label licenses", "description": "What an agent may do once something is classified this way.", "questions": [ { "id": "consequence-record-q01", "text": "What follows practically once something is treated as Bitcoin?", "kind": "action" }, { "id": "consequence-record-q02", "text": "What must an agent not infer from the label alone?", "kind": "action" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a Bitcoin 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 Bitcoin and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Bitcoin, 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 Bitcoin, 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 Bitcoin 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 Bitcoin is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Bitcoin, 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 Bitcoin, 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 Bitcoin 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 } } } }