Making Trust Verifiable Through Evidence, Custody, Status, and Correction: Validity in Nexus Comes From Records, Not Assertion
Nexus Consortium defines Validity by Record as the constitutional doctrine that every material Nexus claim, status, maturity label, recognition, technical output, finance-readiness note, insurance-relevance record, public-safe summary, stakeholder artifact, public authority reference, community record, workforce record, sponsorship reference, Nexus Universe output, Nexus Core output, Nexus Network status, Nexus Rails record, and lawful continuation pathway is valid only to the extent it is supported by a governed record.
Validity by Record is the trust architecture of Nexus.
Nexus operates in a global environment where claims are often created faster than evidence. Institutions announce partnerships before boundaries are clear. Technology providers demonstrate systems before limitations are recorded. Resilience projects are described as bankable before evidence is mature. Insurance discussions are framed as protection solutions before underwriting, affordability, exposure, vulnerability, and basis risk are understood. Public authority participation is used as a signal before approval exists. Community engagement is cited before consent or safeguards are established. Workforce dialogue is referenced before representation is clarified. Sponsors are recognized before contribution boundaries are recorded. Reports become public before decision-use labels are attached. Dashboards circulate before uncertainty and data sensitivity are clear.
Nexus cannot operate on that basis.
In Nexus, trust must be record-bearing. A claim does not become valid because a senior person made it, a respected institution attended, a sponsor supported it, a government was present, a dashboard displayed it, a public article described it, a badge was issued, a technology was demonstrated, a financial actor showed interest, or an event gave it visibility.
A claim is valid only when a record exists, the record has a steward, the evidence basis is defined, the decision-use label is attached, permitted claims are stated, prohibited claims are stated, public-safe status is known, correction history is available, and the continuation pathway is bounded.
This doctrine gives practical force to Validity by Record, Nexus Registry, Nexus Claims Discipline, Built to Correct, Authority by Boundary, Non-Execution Doctrine, and Nexus Governance.
The Doctrine in One Sentence
No Nexus claim shall be treated as valid unless it is supported by a record that states what the claim is, what evidence supports it, what scope applies, what decision-use label governs it, what public language is permitted, what claims are prohibited, who stewards it, what correction history exists, and what lawful continuation pathway may exist.
This sentence defines the doctrine.
It means participation is not valid as endorsement unless the record says endorsement exists, and Nexus public-good records ordinarily shall not create endorsement.
It means recognition is not valid as certification unless a competent certification framework exists, and Nexus recognition ordinarily shall not create certification.
It means maturity is not valid as approval unless a competent approving authority separately creates approval, and Nexus maturity status ordinarily shall not create approval.
It means technical readiness is not valid as technology validation unless the record defines validation under a competent framework, and Nexus technical-readiness notes ordinarily shall not certify performance.
It means finance-readiness is not valid as investment readiness unless separately established by competent financial actors under lawful frameworks, and Nexus finance-readiness notes shall not provide investment advice.
It means insurance relevance is not valid as underwriting unless an insurer or competent risk-transfer actor separately undertakes underwriting, and Nexus insurance-relevance records shall not underwrite.
It means public authority learning is not valid as government adoption unless a competent public authority separately adopts it.
It means community participation is not valid as consent.
It means workforce dialogue is not valid as union representation.
It means lawful continuation is not valid as implementation authorization.
The record governs the meaning.
If the record does not support the claim, the claim shall not stand.
Why Validity by Record Is Necessary
The global resilience and innovation ecosystem is full of weak signals that can be misused as strong claims.
A meeting can be turned into a partnership claim.
A partnership can be turned into endorsement language.
A demonstration can be turned into certification language.
A readiness note can be turned into approval language.
A public-safe summary can be turned into official guidance.
A finance-readiness conversation can be turned into investment signaling.
An insurance-relevance discussion can be turned into insurability language.
A recognition badge can be turned into market standing.
A sponsor logo can be turned into influence.
A public authority name can be turned into government support.
A community record can be turned into consent.
A workforce record can be turned into representation.
An event outcome can be turned into institutional proof.
Nexus cannot rely on reputation to control these risks. It requires records.
Validity by Record is necessary because Nexus operates as a public-good conversion rail. It converts risk into demand, demand into portfolios, portfolios into evidence, evidence into readiness, readiness into stakeholder artifacts, artifacts into decision-use labels, and labeled records into public-safe intelligence, finance-readiness, insurance relevance, or lawful continuation. Every step requires record custody.
Without records, conversion becomes narrative.
Without records, public-safe language becomes fragile.
Without records, correction becomes imprecise.
Without records, recognition becomes inflationary.
Without records, public authority boundaries become ambiguous.
Without records, finance and insurance language becomes unsafe.
Without records, Nexus cannot prove what it did, what it did not do, what it meant, what it prohibited, and what can be corrected.
Validity by Record is therefore a constitutional discipline, not an administrative preference.
The Difference Between Evidence, Record, and Claim
The doctrine requires clarity among three terms: evidence, record, and claim.
Evidence is the underlying support for a statement, finding, status, artifact, or pathway. Evidence may include data, documents, models, simulations, observations, stakeholder inputs, public authority records, community knowledge, workforce records, technical methods, loss data, infrastructure data, standards references, legal review, financial analysis, or other material support.
A record is the governed container that organizes evidence, scope, status, decision-use label, permitted claims, prohibited claims, steward, correction history, and continuation pathway.
A claim is what may be said or used based on the record.
Evidence alone is not enough. Evidence must be governed.
A record alone is not enough. The record must specify what claims it permits.
A claim alone is never enough. The claim must be traceable to a record.
This distinction is central to Nexus.
A model output is evidence, but it is not automatically a valid public claim.
A simulation record may support technical learning, but not official warning.
A public authority meeting note may support a learning record, but not government adoption.
A community input may support a participation record, but not consent.
A finance-readiness analysis may support capital readability, but not investment advice.
An insurance-relevance note may support protection-gap understanding, but not underwriting.
Validity arises only when evidence, record, and claim are correctly connected.
The Minimum Record Standard
Every material Nexus record should include a minimum set of elements.
Record Identity
The record must have a unique record ID, title, record type, ontology class, version number, date of creation, and responsible steward.
This prevents ambiguity and allows the record to be referenced, updated, corrected, superseded, withdrawn, or archived.
Record Scope
The record must state its purpose, subject matter, geographic scope where applicable, stakeholder scope, portfolio relationship, time period, and limitations.
Scope prevents overuse.
Evidence Basis
The record must identify its evidence basis. This may include data sources, method notes, model assumptions, stakeholder inputs, public authority references, technical records, community records, workforce records, finance-readiness sources, insurance-relevance sources, and legal or governance review where applicable.
The evidence basis must also state uncertainty, data quality, exclusions, and known gaps where material.
Data Classification
The record must classify data sensitivity. Classes may include public, public-safe, internal, controlled, confidential, restricted, sovereign-sensitive, rights-bearing, critical infrastructure-sensitive, commercially sensitive, competition-sensitive, or other defined classes.
Data classification determines access, publication, AI use, retention, transfer, compute-to-data requirements, and public-safe communication.
Decision-Use Label
The record must include a decision-use label, such as Learning Only, Internal Planning Support, Public-Safe Communication, Technical Review Support, Finance-Readiness Support, Insurance-Relevance Support, Public Authority Decision Support, or Enterprise Continuation Support.
The decision-use label defines permitted use.
Public-Safe Status
The record must state whether it is internal, controlled, public-safe, media-safe, participant-facing, public authority-facing, finance-facing, insurance-facing, archived, withdrawn, or restricted.
Public-safe status prevents uncontrolled publication.
Permitted Claims
The record must state what may be said based on the record.
Permitted claims should be precise, scope-bound, and boundary-safe.
Prohibited Claims
The record must state what must not be said.
Prohibited claims may include certification, approval, endorsement, official warning, investment advice, underwriting, procurement preference, public authority decision, community consent, worker representation, professional reliance, guarantee, or implementation authorization.
Stewardship
The record must identify who stewards the record, who may update it, who may approve publication, who may correct it, and who may archive it.
Correction History
The record must include correction history, including corrections, clarifications, supersession, downgrades, restrictions, suspensions, withdrawals, archives, and re-entry where applicable.
Related Records
The record should identify related risk signals, portfolios, evidence registers, technical-readiness notes, public-safe summaries, finance-readiness notes, insurance-relevance records, stakeholder artifacts, public authority boundary labels, community safeguards records, workforce records, sponsor records, recognition records, and continuation records.
Lawful Continuation Pathway
Where applicable, the record must identify possible lawful continuation routes without implying authorization.
This minimum record standard makes Nexus validity operational.
Validity by Record and Nexus Rails
Nexus Rails is the continuous infrastructure that carries Validity by Record.
Without Nexus Rails, records can become disconnected. A public-safe summary may separate from its evidence. A finance-readiness note may circulate without its prohibited claims. A public authority learning record may be quoted without its boundary label. A technical-readiness note may be reused after it is superseded. A recognition may remain visible after it is withdrawn. A Nexus Universe output may be used outside its decision-use label. A Nexus Core simulation may be treated as current after a new model version replaces it.
Nexus Rails prevents this by maintaining the link between record, evidence, status, decision-use label, public-safe status, correction history, and continuation pathway.
Nexus Rails for Development Finance shows why this matters in finance-facing contexts. Development finance readiness depends on records that remain traceable, versioned, and bounded. A record that cannot be traced cannot safely inform finance-readiness. A record that lacks prohibited claims can become financial overclaim. A record that lacks correction history can become stale authority.
Nexus Rails is therefore not merely an operating system. It is the custody layer for validity.
Validity by Record and Nexus Registry
The Nexus Registry is the record-bearing infrastructure through which Nexus validity becomes visible and governable.
The registry does not create certification by listing a record. It does not create public authority approval. It does not create procurement status. It does not create financeability, bankability, insurability, market standing, or implementation authority.
The registry creates traceability.
It allows stakeholders to see whether a claim has a record, whether the record is current, what status applies, what decision-use label governs it, what evidence supports it, what claims are permitted, what claims are prohibited, whether the record has been corrected, and whether the record has been archived.
A registry entry should never be framed as approval. It should be framed as custody.
This is why registry language must remain public-safe.
Validity by Record and Nexus Reports
Nexus Reports should be understood as reporting outputs derived from records, not substitutes for records.
A report may summarize findings, readiness, maturity, gaps, stakeholder artifacts, public-safe intelligence, correction history, or continuation pathways. But the report itself must identify its evidence base, record references, decision-use labels, public-safe status, permitted claims, prohibited claims, and correction pathway.
A report should not convert records into broader claims.
A public report should not reveal controlled data.
A finance-facing report should not provide investment advice.
An insurance-facing report should not imply underwriting.
A public authority-facing report should not imply adoption.
A technical report should not imply certification.
A community-facing report should not imply consent.
Reports are useful when they remain anchored in records.
Validity by Record and GCRI
GCRI’s technical role requires strict record validity.
The Global Centre for Risk and Innovation may support technical backbone functions, evidence infrastructure, methods, ontology, observability, public-good R&D, Nexus Core, Nexus Observatory, Nexus Standards, Nexus Risk Management, Nexus Registry, Nexus Reports, Nexus Academy, Nexus Labs, Nexus Foundry, Nexus Agency, and Verifiable Compute and Verifiable Intelligence.
Every GCRI technical claim must be record-based.
A Nexus Observatory insight should identify source, scope, uncertainty, and decision-use label.
A Nexus Standards note should identify whether it is guidance, protocol, controlled vocabulary, interoperability reference, or public-safe summary.
A Nexus Risk Management output should identify evidence basis and boundaries.
A Nexus Core simulation should identify model version, assumptions, data quality, validation limits, uncertainty, decision-use label, and correction history.
A Nexus Labs or Nexus Foundry output should identify whether it is a challenge brief, demo label, model evaluation record, technical-readiness note, or public-safe summary.
A GCRI technical assistance output should identify what it supports and what it does not authorize.
GCRI’s technical credibility depends on refusing unsupported technical claims.
Validity by Record and GRF
GRF’s public-facing role requires record-based legitimacy.
The Global Risks Forum may support public-good legitimacy, councils, stakeholder formation, registry, recognition, maturity records, public-safe reporting, participation pathways, public trust, diplomacy, policy learning, foresight, community participation, media discipline, and whole-of-society mobilization.
Every GRF public claim should be supported by records.
A council role should have a participation record.
A recognition should have a recognition record.
A public-safe summary should have source records and review status.
A public authority reference should have a boundary label.
A community participation statement should have safeguards records.
A workforce statement should have representation boundary.
A national mobilization statement should have scope and decision-use label.
GRF pathways such as Nexus Governance Councils, Leadership Council, Academia and Universities Council, Industry and Standards Council, State and Government Council, Community and Indigenous Council, Media and Civil Society Council, GRF Participation Pathways, and Joining GRF should preserve this doctrine.
GRF legitimacy is valid by record, not by visibility.
Validity by Record and GRA
GRA’s finance and insurance-facing role requires precise record validity.
The Global Risks Alliance may support finance-readiness, capital readability, investor literacy, insurance relevance, protection-gap understanding, diligence translation, financial-services common-business-interest learning, and finance-facing knowledge products.
Every GRA finance or insurance-facing claim must be supported by a record.
A finance-readiness note must state evidence maturity, scope, public authority context, safeguards, technical readiness, decision-use label, prohibited claims, and correction history.
A capital readability record must not be represented as a rating.
An insurance-relevance record must state hazard, exposure, vulnerability, loss basis, risk-reduction evidence, affordability, basis risk, trigger relevance, public finance context, and limits.
A protection-gap record must not be represented as coverage.
A recognition record must not be represented as market standing.
GRA pathways such as Insurance Nexus, Banking Nexus, Asset Management Nexus, Capital Markets, Development Finance, Private Equity Nexus, Institutional Funds Nexus, Financial Regulations Nexus, Sovereign and Public Finance, Critical Systems Finance, and Knowledge Products must maintain record discipline.
GRA credibility is valid by record, not by capital language.
Validity by Record and Nexus Universe
Nexus Universe must be record-producing, not only visible.
Every Nexus Universe room, track, challenge, forum, learning session, technical demonstration, finance-readiness discussion, insurance-relevance discussion, public authority engagement, community forum, workforce forum, sponsor desk, recognition activity, Nexus Core operation, Nexus Network formation room, and lawful continuation discussion should produce records where material.
A national resilience room should produce portfolio records, public authority learning records, and maturity updates.
An early warning support room should produce gap records, warning-authority boundary labels, and anticipatory action readiness notes.
A finance room should produce finance-readiness notes, not investment advice.
An insurance room should produce insurance-relevance records, not underwriting conclusions.
A technology challenge should produce demo labels, model evaluation records, interoperability records, and technical-readiness notes, not vendor certification.
A community forum should produce participation and safeguards records, not consent.
A workforce forum should produce exposure and social dialogue records, not representation.
A sponsor desk should produce sponsor firewall records, not influence claims.
If Nexus Universe produces attention without records, it has not satisfied Validity by Record.
Validity by Record and Nexus Core
Nexus Core must be valid by technical record.
A Nexus Core output should never stand alone as a screenshot, dashboard, presentation, model result, AI output, or simulation image. It must be attached to a technical record.
The technical record should state:
What was modeled or tested.
What data was used.
What data was excluded.
What assumptions were made.
What model or workflow was used.
What version applied.
What uncertainty exists.
What validation limits apply.
What technical-readiness status exists.
What cybersecurity controls applied.
What data classification applies.
What public-safe status applies.
What decision-use label governs use.
What claims are permitted.
What claims are prohibited.
What correction pathway exists.
What lawful continuation route may exist.
This is the technical expression of Verifiable Compute and Verifiable Intelligence.
Nexus Core produces value only when its outputs can be traced, reviewed, bounded, corrected, and carried through Nexus Rails.
Validity by Record and Nexus Network
Nexus Network nodes must also be valid by record.
A node is not valid because it is announced.
A node is not valid because a host is interested.
A node is not valid because a country is named.
A node is not valid because stakeholders attended a launch.
A node is valid only when its governance charter, host or anchor record, public authority interface, data obligations, cybersecurity baseline, claims rules, funding model, maturity status, review cycle, correction pathway, suspension process, public-safe communication rules, Nexus Rails relationship, and lawful continuation boundaries are recorded.
A national node that lacks a public authority boundary record is unsafe.
A technical node that lacks data obligations is unsafe.
A finance-readiness node that lacks financial overclaim boundaries is unsafe.
An insurance-relevance node that lacks underwriting boundaries is unsafe.
A community node that lacks safeguards is unsafe.
A workforce node that lacks representation boundaries is unsafe.
Validity by Record prevents node announcements from becoming false authority.
Validity by Record and Recognition
Recognition is especially vulnerable to misuse. It must be valid by record.
A badge is not the record.
A certificate-like image is not the record.
A public profile is not the record.
A website listing is not the record.
The record must state what was recognized, why it was recognized, what evidence supports the recognition, what scope applies, what the recognition does not imply, what decision-use label applies, what public language is permitted, what claims are prohibited, whether the recognition is current, and what correction pathway applies.
Recognition must not imply certification, endorsement, public authority approval, procurement qualification, professional status, market standing, financeability, bankability, insurability, or implementation authority.
GRA’s Recognition Records, Badges, and Contribution Proof should be read through this doctrine.
Recognition is valid only when the underlying record is valid.
Validity by Record and Public Authority Claims
Public authority-related claims require heightened record discipline.
A government, ministry, regulator, city, public agency, central bank, financial supervisor, disaster agency, meteorological service, hydrological service, public health authority, procurement authority, or public institution should not be referenced publicly without a boundary record where the reference could imply authority.
The record should state whether the public body attended, observed, contributed, reviewed, co-hosted, sponsored, formally authorized, or merely received information.
It should also state what is not implied: no adoption, no approval, no endorsement, no public authority decision, no official warning, no regulatory guidance, no procurement authorization, no fiscal advice, no financing approval, no insurance approval, no sovereign representation, and no implementation authorization.
GRF’s State and Government Council and National Mobilization must preserve this record discipline.
Validity by Record and Community Claims
Community claims must be valid by record.
A community participation claim requires a participation record.
A local knowledge claim requires a local knowledge protocol.
A rights-sensitive claim requires rights-bearing data classification.
A public-safe community summary requires public-safe review.
A grievance claim requires a grievance route record.
A benefit claim requires a benefit and burden note.
A conflict-sensitive claim requires a conflict sensitivity record.
Community participation is not consent.
Indigenous participation, where applicable, is not FPIC, treaty compliance, land-rights determination, or lawful consultation completion unless competent lawful processes separately establish that status.
GRF’s Community and Indigenous Council and Media and Civil Society Council should preserve this doctrine.
Validity by Record and Workforce Claims
Workforce claims must be valid by record.
A workforce exposure claim requires an exposure register.
A social dialogue claim requires a social dialogue record.
A worker participation claim requires a participation record and representation boundary.
A just transition claim requires a blueprint with evidence, scope, safeguards, and limitations.
An occupational health and safety claim requires a note that does not imply employer compliance unless separately established.
Worker participation is not union representation unless separately authorized.
A social dialogue record is not collective bargaining.
A workforce exposure note is not employer compliance.
A just transition blueprint is not policy approval.
Validity by Record protects workers from symbolic inclusion and status overclaim.
Validity by Record and Sponsor Claims
Sponsor claims must be valid by record.
A sponsor contribution record should state who contributed, what was contributed, what the contribution supports, what it does not control, what public language is permitted, what procurement non-reliance applies, what recognition is permitted, what data or IP conditions apply, what conflict management applies, and what correction pathway exists.
Sponsor support is not control.
Sponsor visibility is not endorsement.
Sponsor contribution is not procurement preference.
Sponsor recognition is not market standing.
Sponsor funding is not agenda authority.
A sponsor claim without a sponsor firewall record is not Nexus-compliant.
Validity by Record and Public-Safe Language
Public-safe language must be traceable to records.
A public article, public-safe summary, media-safe statement, social post, report excerpt, recognition page, council page, sponsor page, technology challenge page, Nexus Universe page, Nexus Core page, Nexus Network page, or GRA finance-facing page should not make material claims that cannot be traced to records.
Public-safe language should use phrases such as recorded, reviewed within stated scope, technical-readiness note, finance-readiness note, insurance-relevance record, public authority learning record, participation record, recognition record, maturity status, decision-use label, public-safe summary, correction notice, and lawful continuation pathway.
It should avoid phrases such as certified, approved, endorsed, official, guaranteed, bankable, insurable, investable, procurement-ready, implementation-ready, government-approved, underwritten, rated, community-consented, union-supported, socially licensed, and equivalent language unless a competent institution has separately and lawfully created such status and the record expressly permits it.
Validity by Record and Legal Operating Architecture
Record validity must be supported by legal and regulatory discipline.
Records that may affect public authority, procurement, finance, insurance, professional reliance, data rights, IP, sponsorship, community rights, labor representation, public communications, or implementation should be reviewed through an appropriate legal operating architecture.
That architecture should address entity role mapping, jurisdictional review, contracts, liability, professional reliance boundaries, data processing agreements, cross-border transfers, sanctions and export controls, anti-bribery and anti-corruption, procurement integrity, competition law, financial promotion, insurance and risk-transfer boundaries, lobbying and political activity boundaries, IP, data rights, insurance coverage, dispute resolution, document retention, and public communications control.
A record is not legally safe merely because it is well written. It must be safe within its operating context.
Validity by Record Failure Modes
The doctrine must identify failure modes.
Assertion failure occurs when claims are made without records.
Reputation failure occurs when institutional prestige substitutes for evidence.
Visibility failure occurs when event presence substitutes for status.
Badge failure occurs when recognition graphics substitute for recognition records.
Dashboard failure occurs when visual outputs substitute for evidence registers.
Simulation failure occurs when model outputs substitute for technical-readiness records.
Finance failure occurs when finance-readiness language substitutes for investment analysis or advice.
Insurance failure occurs when insurance relevance substitutes for underwriting.
Public authority failure occurs when attendance substitutes for approval.
Community failure occurs when participation substitutes for consent.
Workforce failure occurs when dialogue substitutes for representation.
Sponsor failure occurs when contribution substitutes for control or endorsement.
Node failure occurs when node announcements substitute for governance charters.
Correction failure occurs when records are not versioned, corrected, superseded, withdrawn, or archived.
Validity by Record exists to prevent these failures.
Validity-by-Record Test
Every Nexus instrument must answer:
What claim is being made?
What record supports the claim?
What evidence supports the record?
What is the record ID?
Who stewards the record?
What is the version and date?
What scope applies?
What decision-use label applies?
What data classification applies?
What public-safe status applies?
What claims are permitted?
What claims are prohibited?
What is not implied?
Does the record imply no public authority approval?
Does the record imply no certification?
Does the record imply no procurement preference?
Does the record imply no investment advice or financing approval?
Does the record imply no underwriting or insurance approval?
Does the record imply no professional reliance?
Does the record imply no community consent?
Does the record imply no workforce or union representation?
Does the record imply no sponsor control?
Does the record imply no implementation authorization?
What correction pathway exists?
What supersession, withdrawal, suspension, downgrade, or archive pathway exists?
What lawful continuation route may exist?
If a Nexus instrument cannot answer these questions, it shall not be used as a basis for public claim, recognition, maturity status, finance-readiness, insurance relevance, Nexus Universe output, Nexus Core output, Nexus Network node, Nexus Rails record, or Enterprise Stack continuation reference.
Final Validity-by-Record Doctrine Statement
Validity by Record is the doctrine that makes Nexus trust verifiable.
It prevents assertion from becoming truth.
It prevents reputation from becoming evidence.
It prevents participation from becoming endorsement.
It prevents recognition from becoming certification.
It prevents maturity from becoming approval.
It prevents technical readiness from becoming validation.
It prevents simulation from becoming real-world proof.
It prevents finance-readiness from becoming investment advice.
It prevents insurance relevance from becoming underwriting.
It prevents public authority learning from becoming government adoption.
It prevents community participation from becoming consent.
It prevents workforce dialogue from becoming representation.
It prevents sponsorship from becoming control.
It prevents lawful continuation from becoming Nexus authorization.
It requires every material Nexus claim to be attached to evidence, record identity, status, decision-use label, permitted claims, prohibited claims, correction history, and lawful continuation boundaries.
It relies on GCRI for technical record integrity, GRF for public-good status and participation record integrity, and GRA for finance-readiness and insurance-relevance record integrity.
It uses Nexus Universe to generate records, Nexus Core to produce verifiable technical records, Nexus Network to maintain durable capacity records, and Nexus Rails to carry record validity continuously.
This doctrine shall govern every Nexus article, charter, protocol, standard, public-safe summary, evidence register, technical-readiness note, model record, simulation record, recognition record, maturity label, public authority reference, finance-readiness note, insurance-relevance record, community safeguards record, workforce record, sponsorship reference, Nexus Universe output, Nexus Core output, Nexus Network node, Nexus Rails record, and lawful continuation pathway.
Where there is no record, Nexus shall not recognize the claim.
Where the record does not support the claim, Nexus shall correct the claim.
Where the record is current, scoped, labeled, evidence-bearing, public-safe, and correctable, Nexus has created the basis for trust.
That is the Validity-by-Record Doctrine.