{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T20:57:04Z", "providers": [ "Claude" ], "breadth": "written by Claude from model knowledge without web access - no source was read, every claim is a lead to verify", "pass": 2, "wave": 3, "engine": "claude", "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T10:00:00Z", "ingestedAt": "2026-10-06T07:02:39+00:00", "fields": [ "agent_conduct", "ethics", "owners" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-06T19:52:02+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q8789", "registryId": "vr.tr.cryptography", "name": "cryptography", "version": "0.2.0-wave.3", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.KNW" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q8789/", "model": { "registry_id": "vr.tr.cryptography", "name": "cryptography", "purpose": "Let an agent explain cryptography and its main building blocks at a conceptual level, relay standards and recommendations from standards bodies, distinguish cryptography from related fields, and route implementation and security decisions to current standards and qualified practice rather than improvising.", "definition": "The practice and study of techniques for secure communication and data protection in the presence of adversaries, using encryption, digital signatures, hash functions and protocols built on mathematical hardness assumptions; modern cryptography underpins secure web traffic, payments, messaging and digital identity, and is governed by standards, export rules and research on new threats such as quantum computing.", "what_it_is_for": "Confidentiality, integrity, authentication and non-repudiation of information.", "affordances": [ "explain concepts and building blocks", "relay standards and recommendations", "distinguish cryptography from cryptanalysis, coding and steganography", "route implementation choices to standards and experts" ], "distinguishing_features": [ "Security defined against adversaries", "Based on hardness assumptions", "Standardised primitives and protocols", "Continuous evolution against new attacks" ], "appearance": "Not visible; algorithms and protocols in software and hardware.", "visual_identification": [ "Mathematical techniques for security against adversaries", "Symmetric, asymmetric and hash primitives", "Cryptocurrency mining and cybersecurity in general are related but distinct" ], "physical_properties": [], "families_and_kinds": [ "symmetric encryption", "public key cryptography and digital signatures", "hash functions and message authentication", "cryptographic protocols such as TLS", "post-quantum cryptography", "applied areas such as white-box cryptography and cryptovirology as research topics" ], "related_models": [ { "relation": "is a kind of", "target": "security engineering", "why": "a discipline within it" }, { "relation": "is contrasted with", "target": "cryptanalysis", "why": "the study of breaking ciphers" }, { "relation": "is used in", "target": "information security", "why": "the application field" }, { "relation": "is standardised by", "target": "National Institute of Standards and Technology", "why": "and other bodies" } ], "identifiers": [ { "scheme": "standard identifiers", "value_or_pattern": "FIPS and NIST SP numbers, RFC numbers", "note": "for algorithms and protocols" } ], "standards_and_regulation": [ "NIST FIPS and SP 800 series", "IETF RFCs for protocols such as TLS", "ISO/IEC 18033 and related standards", "Export control rules and national encryption laws" ], "failure_modes_and_hazards": [ "Home-made or misused algorithms", "Weak keys and poor randomness", "Deprecated algorithms still in use", "Agents advising on operational attacks or bypassing protections" ], "in_scope": [], "out_of_scope": [], "characteristics": [], "agent_conduct": { "may": [ "Use well-reviewed, standard cryptographic libraries and algorithms in systems it is authorized to build.", "Explain cryptographic concepts and the status of algorithms with sources." ], "must_not": [ "Design home-made cryptography for real protection or present it as secure.", "Help break encryption protecting data the user has no right to access.", "Use deprecated algorithms or weak keys for new systems.", "Store or expose private keys outside secure storage." ], "requires_human": [ "Rotating or revoking keys that others depend on.", "Deciding on lawful access to encrypted data." ] }, "ethics": { "considerations": [ "Cryptography protects privacy, money and dissidents; weakening it harms many people.", "It can also hide crime, which makes lawful access debates hard." ], "affected_parties": [ "Users of secure systems", "Journalists and activists", "Organisations holding data" ] }, "owners": { "steward": "Nobody owns the field; key holders answer for their keys.", "master_systems": [] } }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q8789: cryptography", "url": "https://www.wikidata.org/wiki/Q8789", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Cryptography", "url": "https://en.wikipedia.org/wiki/Cryptography", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "concept", "name": "Concept", "description": "What cryptography is.", "rationale": "Definition.", "layers": [ { "id": "definition", "name": "Definition", "description": "Goals and primitives.", "findings": [ { "id": "definition-finding", "name": "Definition", "description": "Definition.", "questions": [ { "text": "What are the goals of cryptography, and what primitives achieve them?", "kind": "definition" }, { "text": "Is the question about cryptography, cryptanalysis, cybersecurity or cryptocurrency?", "kind": "boundary" } ] } ] }, { "id": "assumptions", "name": "Assumptions", "description": "Hardness assumptions.", "findings": [ { "id": "assumptions-finding", "name": "Assumptions", "description": "Assumptions.", "questions": [ { "text": "On what mathematical assumptions do modern schemes rest, and what is provable security?", "kind": "definition" }, { "text": "Which entry fits a specific primitive?", "kind": "action" } ] } ] } ] }, { "id": "practice", "name": "Practice", "description": "Standards and use.", "rationale": "Practice.", "layers": [ { "id": "standards", "name": "Standards", "description": "Standards.", "findings": [ { "id": "standards-finding", "name": "Standards", "description": "Standards.", "questions": [ { "text": "Which standards and recommendations govern algorithm choice and key sizes?", "kind": "provenance" }, { "text": "Which entry fits a specific standard?", "kind": "action" } ] } ] }, { "id": "protocols", "name": "Protocols", "description": "Protocols.", "findings": [ { "id": "protocols-finding", "name": "Protocols", "description": "Protocols.", "questions": [ { "text": "How do protocols such as TLS combine primitives, in general terms?", "kind": "provenance" }, { "text": "Is the user asking how to bypass a protection or attack a system, which the model declines?", "kind": "boundary" } ] } ] } ] }, { "id": "threats", "name": "Threats", "description": "Attacks and evolution.", "rationale": "Care.", "layers": [ { "id": "attacks", "name": "Attacks", "description": "Classes of attack.", "findings": [ { "id": "attacks-finding", "name": "Attacks", "description": "Attacks.", "questions": [ { "text": "What classes of attack exist at a conceptual level, and why do algorithms get deprecated?", "kind": "provenance" }, { "text": "Which references are standard?", "kind": "provenance" } ] } ] }, { "id": "quantum", "name": "Quantum", "description": "Post-quantum transition.", "findings": [ { "id": "quantum-finding", "name": "Quantum", "description": "Quantum.", "questions": [ { "text": "How does quantum computing threaten current schemes, and what is the post-quantum transition?", "kind": "provenance" }, { "text": "Which entry fits post-quantum cryptography?", "kind": "action" } ] } ] } ] }, { "id": "context", "name": "Context", "description": "Law, history and teaching.", "rationale": "Context.", "layers": [ { "id": "law", "name": "Law", "description": "Law and policy.", "findings": [ { "id": "law-finding", "name": "Law", "description": "Law.", "questions": [ { "text": "What laws and debates surround encryption, export and lawful access, with positions attributed?", "kind": "provenance" }, { "text": "Is the presentation neutral?", "kind": "boundary" } ] } ] }, { "id": "history", "name": "History", "description": "History.", "findings": [ { "id": "history-finding", "name": "History", "description": "History.", "questions": [ { "text": "How did cryptography develop from classical ciphers to public key systems?", "kind": "provenance" }, { "text": "Which entry fits the history of cryptography?", "kind": "action" } ] } ] } ] } ] }, "openQuestions": [ "Should each primitive be a separate entry?", "How should standards be linked by version?", "The registry entry has merged aliases for cryptocurrency mining and research subfields; should they be split off?" ], "statistics": { "bundles": 4, "layers": 8, "findings": 8, "questions": 16 } }