Nexus StandardsFinance, insurance and capital marketsRecords and schemas
Finance, insurance and capital markets

Finance, insurance and capital markets: records and schemas

How artifacts of finance, insurance and capital markets are identified, described and resolved: the scope, the record, the categories, the schemas and the catalog entries of the standards that apply. A UNI (Unique Nexus Identifier) identifies; it never certifies. Names of standards bodies and their standards belong to their stewards and are used only to identify the documents; no text of an external standard is reproduced here.

Record explorer · schema, example, crosswalkFrom the registry

Nexus artifact record (NS-1) · 32 fields · 12 required

  • uni required stringThe UNI (Unique Nexus Identifier), NS-1 grammar, without @version.
  • displayAlias stringPublic Nexus Registry short form (NX-R-47092) shown next to the UNI during the transition.
  • registryState enumPublic registry state; corrections keep the UNI and add a version.
  • legacyUni stringDotted UNI v0 this record replaces, for crosswalk (for example grix.eo.stac.catalogue).
  • title required string
  • description string
  • scope required string
  • category required string
  • region string
  • domain stringDOMAIN segment code from registry/domains.yaml (NS-1 v0.2); present when the identifier carries it.
  • sector stringSECTOR segment code from registry/sectors.yaml (NS-1 v0.2).
  • environment enumENV segment code (NS-1 v0.2).
  • contextName stringNS-16 context name: the identifier without CAT and SERIAL; derived, never allocated.
  • systemId stringCanonical systemId from legal/registers/public-identity.json when scope is a SYSTEM.
  • status required enum
  • currentVersion string
  • versions array
    • version string
    • date string
    • gitSha string
    • digest string
    • note string
  • creators required array
    • name string
    • type enum
    • affiliation string
    • orcid string
    • ror string
  • publisherRef required stringEntity reference from legal/registers/legal-entity-profile.yaml; the institution stays publisher of record for institutional artifacts.
  • publicationDate required string
  • language string
  • keywords array
  • rights required object
    • license stringSPDX identifier or LicenseRef-Nexus-Proprietary.
    • rightsHolderRef string
    • accessRight enum
    • embargoDate string
  • legalState required enum
  • claimCeiling required enum
  • locations required array
    • kind enum
    • value string
    • digest string
  • relatedIdentifiers array
    • relation enum
    • identifier string
    • identifierType enum
  • supersededBy string
  • workPackageId string
  • directiveRefs array
  • notes string
  • context objectNS-9: this record is a deployment, instance or programme instance of the concept ofUni, in a context.
    • ofUni string
    • domains arrayids from registry/domains.yaml
    • sectors arrayids from registry/sectors.yaml
    • jurisdictions array
    • hostRef string
    • environment enum
    • validFrom string
    • validUntil string
    • conformsTo arrayNexus Standard ids and registry/external-standards.yaml ids this context claims; evidence per NS-11

Example record · NXS-STD-ST-000001

{ "uni": "NXS-STD-ST-000001", "title": "Nexus Standards NS-1 - the UNI and artifact catalog", "scope": "STD", "category": "ST", "status": "DRAFT", "currentVersion": "0.1.0", "creators": [ { "name": "LEGAL_REVIEW_REQUIRED", "type": "Organizational" } ], "publisherRef": "LEGAL_REVIEW_REQUIRED", "publicationDate": "2026-10-15", "rights": { "license": "LicenseRef-Nexus-Proprietary", "accessRight": "restricted" }, "legalState": "LEGAL_REVIEW_REQUIRED", "claimCeiling": "INTEGRATED", "locations": [ { "kind": "repoPath", "value": "standards/NS-1-identifier-and-artifact-catalog.md" }, { "kind": "repoPath", "value": "registry/nexus-standards.yaml" } ], "workPackageId": "LEGAL-NAME-ARCHITECTURE-001" }
Field crosswalk: Schema.org JSON-LD, DataCite, Zenodo, CodeMeta
Record fieldSchema.orgDataCiteZenodoCodeMetaSource
uniidentifier (PropertyValue, propertyID urn:nexus:uni)alternateIdentifier (alternateIdentifierType NXS)metadata.related_identifiers[] (scheme other)identifierdraft
titlenametitles[].titlemetadata.titlenamedraft
descriptiondescriptiondescriptions[].description (Abstract)metadata.descriptiondescriptiondraft
scope·subjects[] (subjectScheme nexus-scope)metadata.keywords[]·draft
categoryadditionalTypetypes.resourceTypeGeneralmetadata.upload_type / publication_type / image_typeapplicationCategoryregistry
regionspatialCoveragegeoLocations[].geoLocationPlacemetadata.locations[]·draft
statuscreativeWorkStatus··developmentStatusdraft
currentVersionversionversionmetadata.versionversiondraft
versions·relatedIdentifiers (IsNewVersionOf, IsPreviousVersionOf)versions (concept DOI)·draft
creatorscreator / authorcreators[]metadata.creators[]authordraft
publisherRefpublisherpublishermetadata.publisher (Zenodo)publisherdraft
publicationDatedatePublishedpublicationYear; dates[] (Issued)metadata.publication_datedatePublisheddraft
languageinLanguagelanguagemetadata.language·draft
keywordskeywordssubjects[]metadata.keywords[]keywordsdraft
rights.licenselicenserightsList[].rightsIdentifier (SPDX)metadata.licenselicensedraft
rights.accessRightconditionsOfAccess·metadata.access_right·draft
legalState····draft
claimCeiling····draft
locationsurl / contentUrl / codeRepositoryalternateIdentifiers[] (URL)files[] / metadata.related_identifiers[]codeRepository / downloadUrldraft
relatedIdentifiersisPartOf / citation / isBasedOnrelatedIdentifiers[] (relationType)metadata.related_identifiers[]isPartOf / referencePublicationdraft
supersededBy·relatedIdentifiers[] (IsObsoletedBy)metadata.related_identifiers[] (isObsoletedBy)·draft
workPackageId····draft
directiveRefs·relatedIdentifiers[] (References)metadata.related_identifiers[] (references)·draft
context····draft

Rows marked registry come from the categories' Zenodo and DataCite mappings in the registry; rows marked draft are the page engine's reading of the public schemas, not part of the registry.

Record explorerschemas/nexus-artifact-record.v1.json with example records from the STD catalog. Legal state and claim ceiling are honesty fields; a record describes, it never certifies.

01Identifier

UNIs under scope RLS.

RLS is the system scope Participants. An artifact of this area is minted as NXS-RLS-<CAT>-<SERIAL>, with an optional region segment for regional artifacts; serials come only from the catalog.

UNI anatomy · parse, resolve, citeFrom the registry
prefixNXSfixedscope<SCOPE>32 codescat<CAT>38 artifact, 9 record codesregion<REGION>ISO 3166-1 or M49serial<SERIAL>six digits, allocatedversion@<VERSION>semver or record version
NXS-STD-ST-000001NXS-EWS-DS-KEN-000003NXS-GRX-RP-M002-000007@1.2.0NXS-GRX-OB-KEN-000042@3NXS-GCR-AR-000015

Without script: the grammar above and the tables below. With it: type any UNI and each segment is checked against the registry, resolved to its record when the page carries it, and turned into a URN, a resolver link and a citation. Serials are never minted here (NS1-R2).

UNI anatomyThe grammar of NS-1 segment by segment, with the registry's scope and category codes. Resolution is a link to the resolver; nothing is fetched and no serial is minted here.

The form above is a pattern, not an allocated identifier. Codes classify and are never product names.

02Canvas

Record lifecycle.

Canvas · record lifecycleDesign, not a record
Finance, insurance and capital markets: an artifact from minting to citationHow an artifact in this area gets its UNI under scope RLS, carries it in every surface and resolves; the steps NS-1, NS-2, NS-3b, NS-6 and NS-7 specify. A design of the record lifecycle, not an allocated identifier.

Fig.From minting to citation, as NS-1, NS-2, NS-3b, NS-6 and NS-7 specify. Design, not an allocated identifier.

03The record

What every catalog record carries.

Field setValues
Required fieldsuni, title, scope, category, status, creators, publisherRef, publicationDate, rights, legalState, claimCeiling, locations
StatusesDRAFT, PUBLISHED, SUPERSEDED, WITHDRAWN
Legal statesLEGAL_REVIEW_REQUIRED, APPROVED, RESTRICTED, PROHIBITED
Claim ceilingsFIXTURE_VERIFIED, IMPLEMENTATION_COMPLETE, INTEGRATED, LAB_OBSERVED
04Embedding

Where the UNI appears in the artifact itself.

SurfaceHow
sourceFileheader comment: Nexus-UNI: <uni>
markdownfront matter uni: or first line Nexus-UNI: <uni>
datasetmetadata sidecar <file>.uni.json with the record, or a uni key in STAC / DataCite metadata
figurecaption suffix [<uni>] and image metadata
httpApiresponse header X-Nexus-UNI: <uni>
htmlPage<meta name="nexus-uni" content="<uni>"> and data-nexus-uni on the component root
wordpresspost meta _nexus_uni and the block attribute nexusUni; the plugin renders the meta tag
roomroom-binding provenance carries uni for every projected record
05Record kinds

Record kinds and artifact categories.

Artifacts use categories mapped to Zenodo and DataCite; records of the data fabric use record kinds (NS-3). The two lists never share a code.

CodeRecord kind (NS-3)
OBObservation fact
SRSource release
INIndicator definition
MEMeasure definition
BDBoundary version
CTChronotope version
CRCorrection record
APAnalytical product record
SUSubject (place
06Schemas

The machine schemas.

  • nexus-artifact-record.v1.json
  • nexus-attestation.v1.json
  • nexus-clause.v1.json
  • nexus-policy.v1.json
  • nexus-proposal.v1.json
  • nexus-subject-passport.v1.json
07Catalog

Catalog entries of the standards that apply.

Records in the standards scope; legal state and claim ceiling are honesty fields, never readiness claims.

UNITitleCategoryStatusLegal state
NXS-STD-ST-000004Nexus Standards NS-0 - constitution and principlesSTdraftlegal review required
NXS-STD-ST-000005Nexus Standards NS-9 - contextual UNIs (deployments, instances, programme instances)STdraftlegal review required
NXS-STD-ST-000006Nexus Standards NS-10 - policies and clausesSTdraftlegal review required
NXS-STD-ST-000007Nexus Standards NS-11 - verification and monitoringSTdraftlegal review required
NXS-STD-ST-000013Nexus Standards NS-14 - conformance and crosswalk to external standardsSTdraftlegal review required
08Learn and apply

Where Finance, insurance and capital markets is taught, worked on and run.

Risk Academy disciplines that teach Finance, insurance and capital markets, with their courses; the GCRI Canada, The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) subsites that carry those disciplines; and the Nexus Foundry systems the standards name. Mappings are proposed for review (Risk Academy standards map, 2026-10-17); a link says a page on the same subject exists, never an endorsement or a conformance statement; framework names in course titles are named and linked, never reproduced.

Risk Academy

Disciplines and courses

09Questions

Questions and answers.

Who allocates UNIs for finance, insurance and capital markets artifacts?
The catalog of the consumer that owns scope RLS, through the reference command-line tool. Serials are never typed by hand (NS1-R2).
What does the resolver return?
An HTML landing page for browsers or JSON for machines, for published records that are not restricted (NS-7).
Nexus Standards

Shape the standards for finance, insurance and capital markets.

Every standard here is proposed. Changes enter as proposals under NS-13; conformance is shown by attestations under NS-11; nothing on this site is a certification, an approval or a readiness statement.

Nexus Standards documents CC BY 4.0 · tooling Apache-2.0 · counsel review pending (DEC-2026-10-16-NEXUS-STANDARDS-OPEN-LICENCE). External standards are named and linked under their own licences; a UNI (Unique Nexus Identifier) identifies, it never certifies. · Generated from the Nexus Standards corpus at commit 437ae044c5cb (2026-10-17); proposed and open.

Skip to toolbar