{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T11:56:06Z", "providers": [ "Codex", "Grok" ], "missingProviders": [], "pass": 2, "cost": { "grok": { "usd": 0.00291822, "turns": 1, "seconds": 33.0, "error": null }, "codex": { "seconds": 92.8, "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: 01a07bb8-57c6-7b30-82e2-2591c02cf185\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: ISO 4217\nRegistry id: vr.tr.iso-4217\nPlane / domain: INF / INF.MED\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\nA Vercy" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T11:00:00Z", "ingestedAt": "2026-10-06T08:15:33+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "standards_and_regulation", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:30+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q37431", "registryId": "vr.tr.iso-4217", "name": "ISO 4217", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.MED" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q37431/", "model": { "registry_id": "vr.tr.iso-4217", "name": "ISO 4217", "purpose": "Enable an AI agent to recognise ISO 4217 as a maintained currency identification standard, assess which assignments apply in context, and decide whether to accept, translate, preserve or escalate a currency designation.", "definition": "ISO 4217 is the International Organization for Standardization's three-letter alphabetic and three-digit numeric code system that uniquely identifies currencies, funds, and precious metals used in international financial transactions.", "scope_statement": "This model owns the identity, authority, assignment semantics, minor-unit interpretation and amendment lifecycle of ISO 4217 for registry entry vr.tr.iso-4217 in INF / INF.MED, including the evidence needed to apply its codes.", "in_scope": [ "Standard edition and authoritative code-list provenance", "Alphabetic and numeric currency-code assignments and their correspondence", "Distinctions among currency, fund and special-purpose assignments", "Entity associations and limits on inferring geography from codes", "Minor-unit interpretation and explicit treatment of unavailable information", "Assignment changes, historical interpretation and application eligibility" ], "out_of_scope": [ "Currencies as monetary institutions, including issuance and monetary policy", "Exchange rates, valuations and redenomination calculations", "Legal-tender status and jurisdiction-specific payment obligations", "Payment-network support, settlement rules and transaction authorization", "Locale-specific currency symbols, formatting and cash-rounding rules", "Country-code governance and financial instrument or digital-token identification" ], "distinguishing_features": [ "Identify a standard governing currency representations, rather than a particular currency, monetary amount or exchange-rate feed.", "Check for three-letter alphabetic and corresponding three-digit numeric representations, together with minor-unit relationships where applicable. [ISO standard description](https://www.iso.org/standard/64758.html?browse=tc)", "Require an authoritative assignment lookup; a plausible three-letter ticker or currency symbol alone does not establish ISO 4217 membership.", "Distinguish current currency and funds lists from registered funds and historical lists. [SIX currency-code maintenance](https://www.six-group.com/en/products-services/financial-information/market-reference-data/data-standards.html?printout=1)", "Treat a code's identification role separately from claims that the represented unit is legal tender, exchangeable or supported by a payment service." ], "characteristics": [ { "name": "Standard edition", "kind": "category", "unit_or_values": "Verified ISO edition designation; unknown if unverified", "why_it_matters": "Separates the governing specification from subsequent changes to maintained assignments." }, { "name": "Assignment evidence", "kind": "relation", "unit_or_values": "Links to authoritative list snapshots and applicable amendment notices", "why_it_matters": "Makes acceptance or rejection of a designation traceable." }, { "name": "Alphabetic and numeric correspondence", "kind": "relation", "unit_or_values": "Assigned three-letter representation paired with its three-digit representation", "why_it_matters": "Supports translation between representations without deriving assignments from spelling." }, { "name": "Assignment role", "kind": "category", "unit_or_values": "Currency, fund, precious metal, other documented special purpose, or unresolved", "why_it_matters": "Prevents all recognised codes from being treated as ordinary spendable currencies." }, { "name": "Temporal assignment state", "kind": "state", "unit_or_values": "Effective at reference date, announced for future effect, historical at reference date, or unresolved", "why_it_matters": "Supports different decisions for new transactions and historical records." }, { "name": "Listed entity associations", "kind": "relation", "unit_or_values": "Documented associations between a designation and listed entities, qualified by date", "why_it_matters": "Prevents unsupported assumptions that each currency has exactly one country." }, { "name": "Minor-unit exponent", "kind": "measurement", "unit_or_values": "Documented decimal exponent n, where one minor unit equals 10^-n major units; retain explicit not-applicable and unknown states", "why_it_matters": "Supports amount interpretation without conflating zero decimal places with missing information." }, { "name": "List currency", "kind": "state", "unit_or_values": "Checked through a specified amendment or date, superseded, or freshness unresolved", "why_it_matters": "Shows whether a locally available list can support the intended decision." }, { "name": "Consumer acceptance", "kind": "relation", "unit_or_values": "Link to the receiving application's accepted codes and amount conventions", "why_it_matters": "Separates ISO recognition from permission to use a designation in a particular workflow." } ], "affordances": [ "Resolve a supplied designation against an authoritative ISO 4217 assignment at a stated date.", "Translate between alphabetic and numeric representations while preserving the original input and leading zeros.", "Classify a recognised assignment before deciding whether its use fits the requested operation.", "Interpret a documented minor-unit exponent when the receiving interface uses that convention.", "Compare list snapshots and assess which validations or stored interpretations an amendment affects.", "Preserve historical designations and escalate unresolved aliases, conflicting evidence or unsupported application use." ], "agent_conduct": { "may": [ "Look up currency codes from the official list.", "Validate currency codes in data the agent is authorized to edit." ], "must_not": [ "Use withdrawn codes as current.", "Invent codes for unofficial currencies.", "Present codes as recognition of a state." ], "requires_human": [ "Changing codes in financial systems." ] }, "ethics": { "considerations": [ "Errors in codes can misroute payments.", "Currency changes affect people's money." ], "affected_parties": [ "Banks", "Businesses", "Data users" ] }, "owners": { "steward": "The standardization body and its maintenance agency.", "master_systems": [ "The standard's published code lists" ] }, "visual_identification": [ "Three letters such as USD or EUR in financial data.", "Three-digit numeric codes." ], "failure_modes_and_hazards": [ "Payment errors from wrong codes." ], "standards_and_regulation": [ "ISO 4217, Codes for the representation of currencies, International Organization for Standardization." ], "what_it_is_for": [ "ISO 4217 is used in payment messages, accounting records, exchange rate data and commercial systems to identify currencies consistently.", "Its codes help distinguish currencies that share names or symbols and support automated processing across countries.", "Historical records require attention to the validity dates of assignments because currencies and their codes can change." ] }, "sources": [ { "id": "iso-4217-official", "title": "ISO 4217 Currency codes", "url": "https://www.iso.org/iso-4217-currency-codes.html", "what_it_supports": "Official definition and maintenance of the ISO 4217 currency code standard", "url_status": "blocked" }, { "id": "wikipedia-iso-4217", "title": "ISO 4217", "url": "https://en.wikipedia.org/wiki/ISO_4217", "what_it_supports": "Overview of alphabetic and numeric codes, special codes, and historical currencies", "url_status": "live" }, { "id": "wikidata", "title": "Wikidata item Q37431: ISO 4217", "url": "https://www.wikidata.org/wiki/Q37431", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" } ], "structure": { "bundles": [ { "id": "standard-and-maintenance-authority", "name": "Standard and Maintenance Authority", "description": "Identify the governing ISO 4217 specification and the authority behind the assignments being applied.", "rationale": "An edition reference alone cannot establish which maintained code assignments an agent has checked.", "layers": [ { "id": "governing-specification", "name": "Governing Specification", "description": "Establish which specification supplies the interpretation rules.", "findings": [ { "id": "edition-and-rule-basis", "name": "Edition and Rule Basis", "description": "Record the verified edition and distinguish consulted normative provisions from public summaries.", "questions": [ { "text": "Which ISO 4217 edition governs this interpretation, and what evidence establishes its status?", "kind": "provenance", "id": "edition-and-rule-basis-q01" }, { "text": "Which interpretation rules were read in the specification, and which remain supported only by summaries?", "kind": "boundary", "id": "edition-and-rule-basis-q02" } ] } ] }, { "id": "maintained-assignment-evidence", "name": "Maintained Assignment Evidence", "description": "Establish the authority and coverage of the list snapshot.", "findings": [ { "id": "authoritative-list-basis", "name": "Authoritative List Basis", "description": "Record the source list, retrieval context and amendment coverage; SIX identifies itself as the official maintenance agency. [SIX maintenance authority](https://www.six-group.com/en/products-services/financial-information/market-reference-data/data-standards.html?printout=1)", "questions": [ { "text": "Which authoritative list or amendment establishes the assignment being used?", "kind": "provenance", "id": "authoritative-list-basis-q01" }, { "text": "What evidence shows that this snapshot includes changes effective on the decision date?", "kind": "measurement", "id": "authoritative-list-basis-q02" } ] } ] } ] }, { "id": "code-recognition-and-correspondence", "name": "Code Recognition and Correspondence", "description": "Resolve code representations without mistaking syntactic plausibility for assignment.", "rationale": "Currency symbols, vendor tickers and malformed numeric representations can resemble ISO designations while requiring different handling.", "layers": [ { "id": "representation-recognition", "name": "Representation Recognition", "description": "Distinguish a supplied token's form from its authoritative meaning.", "findings": [ { "id": "syntax-versus-assignment", "name": "Syntax Versus Assignment", "description": "Record the original token, any normalization and the evidence that it matches an assignment.", "questions": [ { "text": "Is the input an alphabetic code, numeric code, currency name, symbol or external alias?", "kind": "definition", "id": "syntax-versus-assignment-q01" }, { "text": "After any explicitly recorded normalization, does the token match an authoritative assignment?", "kind": "provenance", "id": "syntax-versus-assignment-q02" }, { "text": "Should an unassigned but syntactically plausible token be rejected or referred for alias resolution?", "kind": "action", "id": "syntax-versus-assignment-q03" } ] } ] }, { "id": "paired-designations", "name": "Paired Designations", "description": "Preserve the meaning shared by the two code representations.", "findings": [ { "id": "verified-code-pair", "name": "Verified Code Pair", "description": "Record the list-backed alphabetic-to-numeric correspondence, retaining all three numeric positions.", "questions": [ { "text": "Which alphabetic and numeric codes identify the same assignment in the selected snapshot?", "kind": "definition", "id": "verified-code-pair-q01" }, { "text": "Can conversion preserve leading zeros and detect a supplied pair whose components disagree?", "kind": "action", "id": "verified-code-pair-q02" } ] } ] } ] }, { "id": "assignment-role-and-entity-context", "name": "Assignment Role and Entity Context", "description": "Establish what a designation represents and what its entity associations actually support.", "rationale": "Recognition must not collapse funds, special-purpose designations and shared currencies into a one-country-one-currency assumption.", "layers": [ { "id": "represented-unit-role", "name": "Represented Unit Role", "description": "Identify the assignment's documented economic or special-purpose role.", "findings": [ { "id": "assignment-purpose", "name": "Assignment Purpose", "description": "Record the assigned name, list membership and documented purpose before allowing currency-like operations.", "questions": [ { "text": "Does this assignment designate a currency, fund, precious metal or another documented purpose?", "kind": "definition", "id": "assignment-purpose-q01" }, { "text": "What authoritative wording limits its interpretation as an ordinary currency?", "kind": "boundary", "id": "assignment-purpose-q02" }, { "text": "Does the requested operation accommodate that role, or require a different model or explicit policy?", "kind": "action", "id": "assignment-purpose-q03" } ] } ] }, { "id": "entity-association-boundaries", "name": "Entity Association Boundaries", "description": "Represent listed associations without inventing territorial exclusivity or legal status.", "findings": [ { "id": "listed-entity-meaning", "name": "Listed Entity Meaning", "description": "Record all relevant listed entities and separate those associations from independently governed monetary facts.", "questions": [ { "text": "Which entities are explicitly associated with this assignment at the reference date?", "kind": "provenance", "id": "listed-entity-meaning-q01" }, { "text": "Would inferring a single country, legal-tender status or universal local acceptance exceed the list's evidence?", "kind": "boundary", "id": "listed-entity-meaning-q02" } ] } ] } ] }, { "id": "minor-unit-and-amount-interpretation", "name": "Minor Unit and Amount Interpretation", "description": "Establish what the listed minor-unit information permits an agent to infer about amount representation.", "rationale": "Incorrect scaling can change an amount's value even when its currency code is recognised.", "layers": [ { "id": "listed-minor-unit", "name": "Listed Minor Unit", "description": "Interpret the listed decimal relationship while preserving absent or inapplicable information.", "findings": [ { "id": "minor-unit-evidence", "name": "Minor Unit Evidence", "description": "Record the documented exponent and distinguish a numeric value from an explicit non-applicable marker or missing evidence.", "questions": [ { "text": "What minor-unit value is documented for this assignment in the relevant snapshot?", "kind": "measurement", "id": "minor-unit-evidence-q01" }, { "text": "Does the source specify an exponent, declare the field inapplicable or leave its meaning unresolved?", "kind": "definition", "id": "minor-unit-evidence-q02" } ] } ] }, { "id": "amount-use-boundaries", "name": "Amount Use Boundaries", "description": "Check the amount convention before applying a minor-unit relationship.", "findings": [ { "id": "scaling-preconditions", "name": "Scaling Preconditions", "description": "Require evidence about major-unit versus minor-unit encoding and delegate rounding or interface exceptions to the relevant model.", "questions": [ { "text": "Does the receiving interface express this amount in major units, ISO minor units or another documented scale?", "kind": "boundary", "id": "scaling-preconditions-q01" }, { "text": "Can the proposed scaling preserve the amount exactly, or does it require a separately authorized rounding rule?", "kind": "action", "id": "scaling-preconditions-q02" }, { "text": "Which external rule governs cash rounding or permitted accounting precision for this use?", "kind": "provenance", "id": "scaling-preconditions-q03" } ] } ] } ] }, { "id": "assignment-lifecycle-and-history", "name": "Assignment Lifecycle and History", "description": "Apply amendments according to their effective timing and preserve historical meaning.", "rationale": "A current-list lookup alone cannot resolve past records or announced changes.", "layers": [ { "id": "amendment-effect", "name": "Amendment Effect", "description": "Distinguish publication timing from the time a change takes effect.", "findings": [ { "id": "dated-assignment-change", "name": "Dated Assignment Change", "description": "Record what an amendment changes, when it takes effect and any unresolved precision in its timing.", "questions": [ { "text": "Does the amendment change a code, name, entity association, minor-unit value or list membership?", "kind": "definition", "id": "dated-assignment-change-q01" }, { "text": "What effective date is stated, and how does it differ from the announcement or retrieval date?", "kind": "measurement", "id": "dated-assignment-change-q02" }, { "text": "Which dependent validations should change when the amendment becomes effective?", "kind": "action", "id": "dated-assignment-change-q03" } ] } ] }, { "id": "historical-resolution", "name": "Historical Resolution", "description": "Interpret older designations without silently rewriting the represented unit.", "findings": [ { "id": "historical-record-continuity", "name": "Historical Record Continuity", "description": "Preserve the original designation and distinguish assignment withdrawal from conversion or legal circulation; an amendment can place a currency in the historical list while describing parallel circulation. [SIX amendment 174](https://www.six-group.com/dam/download/financial-information/data-center/iso-currrency/amendments/dl-currency-iso-amendment-174.pdf)", "questions": [ { "text": "Which assignment evidence supports this designation for the record's own date?", "kind": "provenance", "id": "historical-record-continuity-q01" }, { "text": "Would replacing the historical code change the unit of account or require an independently sourced conversion?", "kind": "boundary", "id": "historical-record-continuity-q02" }, { "text": "Should the designation remain valid for historical interpretation while being restricted for new operational use?", "kind": "action", "id": "historical-record-continuity-q03" } ] } ] } ] }, { "id": "application-decisions-and-exceptions", "name": "Application Decisions and Exceptions", "description": "Translate ISO assignment evidence into a justified decision for a specific consuming workflow.", "rationale": "Standard membership, historical interpretability and operational acceptance answer different questions.", "layers": [ { "id": "contextual-acceptance", "name": "Contextual Acceptance", "description": "Combine assignment status with the consumer's declared requirements.", "findings": [ { "id": "use-eligibility", "name": "Use Eligibility", "description": "Record whether the proposed operation requires recognition, current assignment, a particular assignment role or explicit consumer support.", "questions": [ { "text": "Is the task archival interpretation, display, data interchange or initiation of a new monetary operation?", "kind": "definition", "id": "use-eligibility-q01" }, { "text": "Which consumer rule determines whether this recognised designation is accepted for that task?", "kind": "provenance", "id": "use-eligibility-q02" }, { "text": "Given the date, assignment role and consumer rule, should the agent accept, preserve, reject or escalate it?", "kind": "action", "id": "use-eligibility-q03" } ] } ] }, { "id": "unresolved-code-handling", "name": "Unresolved Code Handling", "description": "Handle aliases and conflicting snapshots without inventing assignments.", "findings": [ { "id": "exception-resolution", "name": "Exception Resolution", "description": "Retain unresolved input and identify the evidence needed to resolve an external alias, stale list or conflicting interpretation.", "questions": [ { "text": "Is the unresolved token an external convention, an assignment absent from the local snapshot or an input error?", "kind": "boundary", "id": "exception-resolution-q01" }, { "text": "What authoritative update or documented external mapping would justify resolving it?", "kind": "provenance", "id": "exception-resolution-q02" }, { "text": "Which operation must remain pending until that evidence is available?", "kind": "action", "id": "exception-resolution-q03" } ] } ] } ] }, { "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-kinds", "name": "Kinds and varieties", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "active national currency codes", "historic (withdrawn) currency codes", "fund codes (ISO 4217-A)", "precious-metal codes (XAU, XAG, XPT, XPD)", "supranational currency codes (EUR, XAF, XOF, XCD)", "testing and special-purpose codes (XTS, XXX)", "minor-unit (fractional) currency designations", "numeric-only currency identifiers" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of ISO 4217 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "scheme": "ISO 4217 alphabetic", "value_or_pattern": "AAA (three uppercase Latin letters)", "note": "Primary currency identifier used in banking and commerce" }, { "scheme": "ISO 4217 numeric", "value_or_pattern": "NNN (three-digit code, 000-999)", "note": "Numeric equivalent, often aligned with ISO 3166-1 numeric country codes" }, { "scheme": "Wikidata", "value_or_pattern": "Q160241", "note": "Wikidata item for the ISO 4217 standard itself" } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of ISO 4217 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "ISO 4217:2015 - International Organization for Standardization (ISO)", "ISO 3166-1 - country codes that ISO 4217 alphabetic codes are typically derived from (ISO)", "SWIFT MT/MX message standards that mandate ISO 4217 currency codes (SWIFT)", "UN/EDIFACT and other EDI standards referencing ISO 4217 (UNECE)" ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of ISO 4217 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Banking systems and SWIFT messages identify the currency of a payment with a three-letter ISO 4217 code (e.g. USD, EUR, JPY).", "Foreign-exchange markets, accounting software, and e-commerce checkout pages display and settle amounts against ISO 4217 codes.", "National statistical offices and central banks publish exchange-rate series keyed to ISO 4217 codes.", "Precious-metal trading uses XAU (gold), XAG (silver), XPT (platinum), and XPD (palladium) as ISO 4217 codes rather than national currencies." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of ISO 4217 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "quantity": "alphabetic code length", "typical_range": "exactly 3", "unit": "characters" }, { "quantity": "numeric code range", "typical_range": "000-999", "unit": "dimensionless code" }, { "quantity": "minor unit (exponent)", "typical_range": "0-4 (commonly 0 or 2)", "unit": "decimal places" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of ISO 4217 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Using a withdrawn historic code (e.g. DEM, FRF) in a live payment after euro adoption causes settlement rejection.", "Confusing similar alphabetic codes (e.g. CNY vs CNH, USD vs USS/USN) routes funds to the wrong instrument.", "Treating the numeric code as a quantity rather than an identifier corrupts financial records.", "Omitting or mis-stating the minor-unit exponent (e.g. treating JPY as having two decimal places) produces 100× amount errors." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of ISO 4217 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "China: CNY is the ISO code for the yuan; CNH is a market convention for offshore yuan and is not an ISO 4217 currency.", "Euro area: national legacy codes (FRF, DEM, ITL, etc.) remain in historic tables but are not valid for new euro-denominated payments.", "CFA franc zones: XOF (West African CFA) and XAF (Central African CFA) share a peg and similar names but are distinct ISO codes and clearing systems.", "Some territories use a national currency under a different ISO code from the political state's own currency (e.g. USD in Ecuador, EUR in Montenegro)." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of ISO 4217 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "name": "ISO 3166-1 alpha-3 country codes", "difference": "ISO 3166-1 names countries (USA, FRA); ISO 4217 names currencies (USD, EUR). Same three-letter shape, different object." }, { "name": "SWIFT BIC (ISO 9362)", "difference": "A BIC identifies a financial institution; an ISO 4217 code identifies the currency of an amount in a message that may also carry a BIC." }, { "name": "ticker symbols (FX pairs, equities)", "difference": "Market tickers such as EURUSD or $ are trading-venue conventions; ISO 4217 codes are the standardised currency identifiers those tickers rest on." }, { "name": "ISO 20022 currency codes / ActiveOrHistoricCurrencyCode", "difference": "ISO 20022 reuses ISO 4217 values but adds message-level enumerations (active vs historic); the code list is ISO 4217, the usage constraint is ISO 20022." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of ISO 4217 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which normative edition and complete amendment baseline should this publication adopt, and has the full specification been read?", "What exact rules govern assignment roles, exceptional code construction and possible code reuse across editions?", "How complete and temporally precise are the available historical lists for reconstructing assignments at arbitrary past dates?", "What precise semantics do authoritative minor-unit markers have for each special-purpose assignment?", "Which target applications require documented departures from ISO minor-unit conventions, restrict recognised codes or use external aliases?" ], "statistics": { "bundles": 7, "layers": 13, "findings": 20, "questions": 39 } }