{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T09:15:32Z", "providers": [ "Codex" ], "missingProviders": [ "Grok" ], "pass": 2, "cost": { "grok": { "usd": null, "turns": null, "seconds": 14.2, "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": 83.5, "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: 01a07b25-7df6-7e71-9ef5-cc643049f96d\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: International Standard Serial Number\nRegistry id: vr.tr.international-standard-serial-number\nPlane / domain: INF / INF.MED\nRegistry definition: (none" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T11:00:00Z", "ingestedAt": "2026-10-06T08:10:23+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:25+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q131276", "registryId": "vr.tr.international-standard-serial-number", "name": "International Standard Serial Number", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.MED" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q131276/", "model": { "registry_id": "vr.tr.international-standard-serial-number", "name": "International Standard Serial Number", "purpose": "Enable an AI agent to recognise an ISSN, verify its assignment to a continuing resource, and decide whether to use it, investigate a mismatch or request an authoritative correction.", "definition": "", "scope_statement": "This model owns the identifier represented by vr.tr.international-standard-serial-number: its expression, validation, assignment evidence, identified resource boundary, linking relationships and fitness for a proposed use.", "in_scope": [ "ISSN syntax, canonical presentation and check-digit validation", "Evidence connecting an ISSN to an authoritative assignment record", "The identified continuing resource, its key title and medium", "Assignment history, conflicting assertions and correction needs", "Relationships to ISSN-L, other medium versions and preceding or succeeding titles", "Conditions for using the ISSN in matching, citation and catalogue workflows" ], "out_of_scope": [ "Editorial content, scholarly quality and reputation of the identified publication", "Individual articles, issues, volumes and their separate identifiers", "Publisher organisations, ownership and contractual rights", "Subscription products, holdings, licences and access entitlements", "Hosting platforms, URLs and digital preservation infrastructure", "Administration of the ISSN Network as an organisation" ], "distinguishing_features": [ "An ISSN has eight positions: seven digits and a final check character that can be a digit or X; passing the modulus-11 check establishes structural validity, not assignment. [ISSN explanation](https://www.issn.org/understanding-the-issn/what-is-an-issn/)", "Its referent is a continuing resource, rather than a particular article or issue; the model must establish that resource boundary before using the identifier.", "An ISSN identifies a medium version; an ISSN-L has the distinct role of grouping medium versions, even when its characters equal one member ISSN. [ISSN-L guidance](https://www.issn.org/understanding-the-issn/assignment-rules/the-issn-l-for-publications-on-multiple-media/)", "An authoritative assignment connects the identifier to a key title, which can include qualifiers distinguishing otherwise identical publication titles. [Key-title explanation](https://www.issn.org/faq/what-is-an-issn/)", "The code does not encode publication origin or content, and possession of an ISSN does not establish content quality. [ISSN explanation](https://www.issn.org/understanding-the-issn/what-is-an-issn/)" ], "characteristics": [ { "name": "Observed and canonical expression", "kind": "category", "unit_or_values": "Original observed string; canonical NNNN-NNNC expression, where N is a digit and C is a digit or X", "why_it_matters": "Supports comparison while preserving evidence of transcription or display errors." }, { "name": "Structural validation result", "kind": "state", "unit_or_values": "Unchecked; malformed; check-digit failure; structurally valid", "why_it_matters": "Prevents a plausible-looking string from being accepted without basic validation." }, { "name": "Assignment verification", "kind": "state", "unit_or_values": "Unverified; authority-confirmed; conflicting evidence; unresolved after lookup", "why_it_matters": "Separates an algorithmically valid number from a supported assignment." }, { "name": "Identified resource", "kind": "relation", "unit_or_values": "Continuing resource linked through its authoritative key title and assignment record", "why_it_matters": "Establishes what the number actually identifies." }, { "name": "Assigned medium", "kind": "category", "unit_or_values": "Medium recorded by the authority, such as print or online; unknown if unverified", "why_it_matters": "Prevents conflating different medium versions of a publication." }, { "name": "Authority-recorded identifier status", "kind": "state", "unit_or_values": "Exact status supplied by the consulted authority, or unknown", "why_it_matters": "Keeps authoritative status distinct from local validation and publication activity." }, { "name": "ISSN-L association", "kind": "relation", "unit_or_values": "Authority-supported linking ISSN and associated medium versions; unresolved if unsupported", "why_it_matters": "Permits grouping versions without treating their identifiers as interchangeable." }, { "name": "Title continuity relationships", "kind": "relation", "unit_or_values": "Documented predecessor, successor, merger, split or other title relationships", "why_it_matters": "Supports historical retrieval without collapsing distinct assignments." }, { "name": "Verification age", "kind": "measurement", "unit_or_values": "Elapsed days since the supporting assignment record was checked", "why_it_matters": "Helps decide whether a consequential use requires another authority lookup." }, { "name": "Observed use alignment", "kind": "state", "unit_or_values": "Matches assigned resource and medium; resource mismatch; medium mismatch; unresolved", "why_it_matters": "Detects a real ISSN displayed on the wrong publication or version." } ], "affordances": [ "Normalise an observed ISSN and validate its check digit while preserving the original evidence", "Look up an assignment and compare its key title and medium with the claimed publication", "Match catalogue records at the identified resource and medium level", "Group medium versions through a verified ISSN-L association", "Follow documented title relationships to retrieve earlier or later publications", "Prepare an assignment or correction request for the responsible ISSN centre when evidence requires authoritative action" ], "agent_conduct": { "may": [ "Validate an ISSN's format and check digit.", "Look up an ISSN in the international register to confirm which serial it identifies.", "Flag a mismatch between an ISSN and a title and request a correction from the issuing centre." ], "must_not": [ "Invent or assign an ISSN; only the ISSN network may assign one.", "Treat a valid check digit as proof that a number was ever assigned.", "Use the print ISSN for an online edition, or the reverse, without noting the medium.", "Print an unassigned or borrowed ISSN to make a publication look established." ], "requires_human": [ "Requesting assignment or correction of an ISSN for a publisher." ] }, "ethics": { "considerations": [ "Fake identifiers help predatory journals pass as legitimate and mislead authors and readers." ], "affected_parties": [ "Authors and readers", "Libraries", "Publishers" ] }, "owners": { "steward": "The ISSN International Centre and national ISSN centres that assign them.", "master_systems": [ "ISSN Register" ] }, "visual_identification": [ "The prefix ISSN followed by eight digits in two groups of four separated by a hyphen.", "The last character may be X, standing for a check value of ten.", "Printed on the cover, masthead or copyright page of a serial." ], "failure_modes_and_hazards": [ "Typing errors that still pass the check digit link the wrong serial.", "Fake ISSNs used to lend credibility to predatory journals." ], "standards_and_regulation": [ "ISO 3297, Information and documentation, International standard serial number (ISSN), International Organization for Standardization." ], "what_it_is_for": [ "An ISSN is used in publishing, libraries and bibliographic databases to identify serials and other continuing resources.", "It supports catalogue matching, subscriptions and citation metadata for resources such as journals and newspapers.", "Different media versions can have different ISSNs, so matching requires checking the assigned resource and format." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q131276: International Standard Serial Number", "url": "https://www.wikidata.org/wiki/Q131276", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: ISSN", "url": "https://en.wikipedia.org/wiki/ISSN", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "issn-expression", "name": "ISSN expression", "description": "Recognise the identifier in text and test its structural integrity.", "rationale": "A transcription error must be distinguished from a valid number used for the wrong resource.", "layers": [ { "id": "observed-expression", "name": "Observed expression", "description": "Preserve how and where the candidate identifier appeared.", "findings": [ { "id": "canonical-issn", "name": "Canonical ISSN", "description": "Record the original string, its surrounding label and any unambiguous formatting normalisation.", "questions": [ { "text": "What exact characters and ISSN or ISSN-L label were observed?", "kind": "provenance", "id": "canonical-issn-q01" }, { "text": "Can the expression be normalised without guessing missing or ambiguous characters?", "kind": "action", "id": "canonical-issn-q02" } ] } ] }, { "id": "check-digit-validation", "name": "Check-digit validation", "description": "Evaluate structural validity independently of assignment evidence.", "findings": [ { "id": "structural-test-result", "name": "Structural test result", "description": "Record whether the candidate passes the format and modulus-11 checks without silently repairing it.", "questions": [ { "text": "Does the candidate have seven initial digits and an allowed final check character?", "kind": "measurement", "id": "structural-test-result-q01" }, { "text": "Does the calculated check character match the observed final character?", "kind": "measurement", "id": "structural-test-result-q02" }, { "text": "If validation fails, what source must be checked before proposing a correction?", "kind": "action", "id": "structural-test-result-q03" } ] } ] } ] }, { "id": "assignment-evidence", "name": "Assignment evidence", "description": "Establish whether the number has a supported ISSN assignment.", "rationale": "Checksum validity and publisher display alone cannot settle authoritative assignment.", "layers": [ { "id": "authority-record", "name": "Authority record", "description": "Connect the candidate to an inspected ISSN authority record.", "findings": [ { "id": "verified-assignment", "name": "Verified assignment", "description": "Record the consulted authority, record reference, access date and evidence actually available.", "questions": [ { "text": "Which inspected ISSN Network record or assignment communication supports this number?", "kind": "provenance", "id": "verified-assignment-q01" }, { "text": "Which assignment details were visible, and which remain inaccessible or unverified?", "kind": "boundary", "id": "verified-assignment-q02" } ] } ] }, { "id": "assignment-discrepancies", "name": "Assignment discrepancies", "description": "Keep identifier status and conflicting claims explicit.", "findings": [ { "id": "status-and-conflict", "name": "Status and conflict", "description": "Preserve authority-supplied status separately from local conclusions and secondary-source assertions.", "questions": [ { "text": "What identifier status does the authority explicitly report?", "kind": "provenance", "id": "status-and-conflict-q01" }, { "text": "Do publisher pages or catalogues assert a different assignment, and what evidence could resolve the conflict?", "kind": "provenance", "id": "status-and-conflict-q02" }, { "text": "Does an unsuccessful lookup leave the assignment unresolved rather than establish that it never existed?", "kind": "boundary", "id": "status-and-conflict-q03" } ] } ] } ] }, { "id": "identified-resource-boundary", "name": "Identified resource boundary", "description": "Determine the continuing resource and medium to which the assignment applies.", "rationale": "Title similarity can conceal different resources, and a correct ISSN can be attached to the wrong medium.", "layers": [ { "id": "key-title-identity", "name": "Key-title identity", "description": "Relate the observed publication name to its authoritative identifying title.", "findings": [ { "id": "title-correspondence", "name": "Title correspondence", "description": "Record the key title, relevant qualifiers and evidence connecting displayed or variant titles to it.", "questions": [ { "text": "What key title and qualifiers accompany this ISSN in the authority record?", "kind": "definition", "id": "title-correspondence-q01" }, { "text": "What evidence shows that the observed publication is this resource rather than another with a similar title?", "kind": "boundary", "id": "title-correspondence-q02" } ] } ] }, { "id": "medium-and-resource-level", "name": "Medium and resource level", "description": "Locate the assignment at the appropriate publication level and medium.", "findings": [ { "id": "referent-fit", "name": "Referent fit", "description": "Test whether the claimed use concerns the assigned continuing resource and version.", "questions": [ { "text": "Which medium does the assignment record identify, and does the observed resource match it?", "kind": "boundary", "id": "referent-fit-q01" }, { "text": "Is the agent identifying the continuing resource, an individual issue or an article?", "kind": "definition", "id": "referent-fit-q02" }, { "text": "If the number appears on another format or edition, what authority evidence supports that use?", "kind": "provenance", "id": "referent-fit-q03" } ] } ] } ] }, { "id": "linking-and-title-history", "name": "Linking and title history", "description": "Represent related medium versions and changes in publication identity.", "rationale": "Agents need to distinguish grouping related resources from asserting that they share one assignment.", "layers": [ { "id": "issn-l-grouping", "name": "ISSN-L grouping", "description": "Represent the designated linking identifier and supported version membership.", "findings": [ { "id": "medium-version-links", "name": "Medium-version links", "description": "Keep the medium-specific ISSN role separate from the ISSN-L role.", "questions": [ { "text": "Which ISSN-L is authoritatively associated with this ISSN?", "kind": "provenance", "id": "medium-version-links-q01" }, { "text": "Does the proposed operation need one medium version or the group of versions?", "kind": "action", "id": "medium-version-links-q02" }, { "text": "Which associated ISSNs are supported by the linking record rather than inferred from matching titles?", "kind": "boundary", "id": "medium-version-links-q03" } ] } ] }, { "id": "title-transitions", "name": "Title transitions", "description": "Track documented changes without assuming identifier continuity.", "findings": [ { "id": "continuity-decision", "name": "Continuity decision", "description": "Record authority-supported title relationships and unresolved changes requiring assessment.", "questions": [ { "text": "What predecessor, successor, merger or split relationships are documented for this assignment?", "kind": "provenance", "id": "continuity-decision-q01" }, { "text": "For an observed title change, has the authority confirmed continued use or a different ISSN?", "kind": "action", "id": "continuity-decision-q02" }, { "text": "Which historical titles and periods must remain distinguishable during retrieval or record matching?", "kind": "boundary", "id": "continuity-decision-q03" } ] } ] } ] }, { "id": "issn-use-decisions", "name": "ISSN use decisions", "description": "Determine whether the available evidence supports a particular identifier operation.", "rationale": "An ISSN can be correctly formed and assigned while still being unsuitable for a proposed match or assertion.", "layers": [ { "id": "matching-and-display", "name": "Matching and display", "description": "Assess use in catalogue reconciliation, citation and publication display.", "findings": [ { "id": "operation-fit", "name": "Operation fit", "description": "Make the intended matching level and limits of the identifier explicit.", "questions": [ { "text": "Would using this ISSN merge records for the same assigned resource and medium, or conceal a version or title difference?", "kind": "action", "id": "operation-fit-q01" }, { "text": "Does the proposed display clearly distinguish the ISSN from an ISSN-L?", "kind": "action", "id": "operation-fit-q02" }, { "text": "Is anyone treating assignment as evidence of quality, ownership or access rights that the identifier does not establish?", "kind": "boundary", "id": "operation-fit-q03" } ] } ] }, { "id": "correction-and-reverification", "name": "Correction and reverification", "description": "Route uncertain or incorrect uses toward an evidence-backed resolution.", "findings": [ { "id": "next-authorised-step", "name": "Next authorised step", "description": "Distinguish local formatting repairs from assignment questions requiring an ISSN centre.", "questions": [ { "text": "Can the issue be resolved by a documented formatting correction, or does it concern the assignment itself?", "kind": "action", "id": "next-authorised-step-q01" }, { "text": "Which responsible ISSN centre and supporting publication evidence are needed for an assignment or correction request?", "kind": "action", "id": "next-authorised-step-q02" }, { "text": "What change or unresolved conflict requires rechecking the authority record before further use?", "kind": "action", "id": "next-authorised-step-q03" } ] } ] } ] } ] }, "openQuestions": [ "Which current ISSN Manual rules distinguish major from minor title changes for the resource types this model must support?", "Which authoritative status terms describe cancelled, suppressed or otherwise problematic assignments, and what uses remain appropriate for each?", "How should separate online formats, language editions, supplements and integrating resources be distinguished under current assignment rules?", "Which ISSN Portal interfaces, access conditions and update mechanisms can support repeatable automated verification?", "Does an existing Vercy world model already own this identifier concept, requiring this registry entry to link to it instead of producing a separate publication?" ], "statistics": { "bundles": 5, "layers": 10, "findings": 10, "questions": 27 } }