> For the complete documentation index, see [llms.txt](https://docs.therisk.global/organization/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.therisk.global/organization/standardization/nexus-sovereignty/i.-foundations/intergenerational-verifiability-and-protocol-longevity.md). # Intergenerational Verifiability and Protocol Longevity ## Intergenerational Verifiability and Time-Resilient Governance in the Nexus Sovereignty Framework ### The Problem of Temporal Fragility in Governance Most governance systems are fragile over time. They are designed to operate in the present, but not to remain verifiable across decades of institutional change, technological transition, political disruption, ecological stress, vendor turnover, data migration, legal reform, and historical reinterpretation. Rules are amended without preserving their operational logic. Policies are replaced without clear lineage. Standards evolve without machine-readable comparison to prior versions. Digital systems become obsolete as platforms, vendors, schemas, and databases change. Public records are stored in brittle formats, fragmented repositories, paper archives, proprietary systems, or cloud environments that may not survive institutional disruption. Governance memory becomes dependent on people, offices, contracts, platforms, and political cycles. This temporal fragility is no longer a secondary administrative concern. It is becoming a systemic risk. Climate adaptation requires governance records that remain intelligible across decades. Biodiversity protection, land stewardship, infrastructure finance, sovereign debt exposure, insurance markets, disaster risk reduction, energy transitions, food security, water allocation, health surveillance, AI safety, digital identity, and critical infrastructure all require decisions made today to remain inspectable in the future. A flood defense built in 2027 may be evaluated in 2045. A biodiversity offset may require monitoring for thirty years. A public health rule adopted during one emergency may shape future response protocols. An AI system deployed today may influence institutional practices long after its original model, vendor, data pipeline, or policy context has changed. A Project SPV may produce records that investors, insurers, regulators, communities, courts, and public authorities need to review years later. Traditional governance often fails this test. Laws may change without archived computational logic. Regulations may be superseded without preserving the evidence that justified them. Public agencies may reorganize. International norms may shift. Governments may change. Institutions may lose records. Vendors may shut down platforms. Cloud environments may be migrated. Data schemas may become unreadable. Public dashboards may disappear. Model versions may be lost. Simulation assumptions may become unrecoverable. Credentials may remain visible but lose their evidence basis. Audit trails may exist only as PDFs, emails, spreadsheets, or proprietary logs. In an age of geopolitical turbulence, ecological volatility, AI-mediated decisions, and increasingly autonomous infrastructure, this fragility is unacceptable. Governance must become time-resilient. It must remain inspectable, explainable, replayable where feasible, and correctable across institutional transitions. It must support not only present verification, but intergenerational verifiability. The Nexus Sovereignty Framework addresses this challenge by embedding time resilience directly into protocol architecture. It treats clauses, credentials, simulations, proof receipts, public-safe outputs, digital twin states, Project SPV evidence, maturity records, and correction events as temporal records. Each record should preserve its origin, version, scope, status, context, dependencies, and correction history so that future actors can understand not only what was decided, but why it was decided, how it was tested, what evidence was available, what uncertainty existed, who reviewed it, how it changed, and which systems depended on it. The doctrine is: **Governance is not trustworthy if it is only verifiable today. It must remain inspectable, explainable, and correctable across time.** ### Intergenerational Verifiability as a Sovereignty Requirement Intergenerational verifiability is the capacity of a governance system to preserve the evidentiary, institutional, computational, legal, and technical meaning of its records across long time horizons. It allows future reviewers to reconstruct the logic of past rules, the status of past credentials, the basis of past simulations, the scope of past proof receipts, the conditions of past public-safe reports, and the evolution of past institutional decisions. This is a sovereignty requirement because sovereign control does not end at deployment. A country, region, community, or institution that cannot inspect its own historical governance logic is not fully sovereign over its infrastructure. If the meaning of a rule is locked inside a vendor platform, if a model’s prior behavior cannot be reconstructed, if a credential’s issuance logic has disappeared, if public-safe outputs cannot be linked to their source records, or if a Project SPV’s resilience evidence cannot be traced after system migration, then institutional control has weakened. Time-resilient governance is also a public-good requirement. Future communities may need to know why infrastructure was built in a certain location, why risk thresholds were chosen, why a safeguard was modified, why a public health measure was adopted, why a climate model was trusted, why an AI rule was changed, or why a readiness record was issued. Without verifiable history, accountability becomes dependent on memory, politics, and archival luck. Intergenerational verifiability requires more than archiving documents. It requires structured temporal records: versioned clauses, signed proof receipts, simulation metadata, credential status histories, data provenance, model lineage, compute environment records, public-safe transformation logs, correction paths, and dependency maps. It also requires semantic continuity so that future systems can understand old records even after schemas, languages, standards, and technologies evolve. In the Nexus Sovereignty Framework, time is therefore not treated as metadata only. Time is a governance dimension. Every material rule, record, credential, simulation, output, and correction must be locatable in time, interpretable in context, and traceable across change. ### Time-Stamped and Versioned Clause Histories Every Smart Clause in the Nexus Sovereignty Framework should have a time-stamped, version-controlled, lineage-preserving history. A clause is not merely the current rule. It is the visible evolution of a rule through time. A mature clause history should include the original source, authoring record, source authority, jurisdictional context, institutional context, domain scope, initial version, subsequent amendments, semantic diffs, simulation records, review records, public-safe implications, adoption status, fork history, dispute records, deprecation status, supersession references, and correction events. Each version should be hashed, signed where appropriate, timestamped, and linked to the actor or governance process that authored, reviewed, adopted, forked, or deprecated it. The purpose of clause history is not bureaucracy. It is institutional memory. A future policymaker should be able to ask which clause governed a credential issued in a given year. An auditor should be able to identify which evidence requirements applied when a readiness record was generated. A regulator should be able to determine whether a system used the correct version at the time of a decision. A public authority should be able to review why a disaster threshold changed. A community steward should be able to inspect how a public-safe mapping clause evolved. A technical architect should be able to see whether an AI agent applied an outdated tool-use rule. A historian or investigator should be able to reconstruct how governance logic changed through crisis, reform, or failure. Clause histories should also preserve jurisdictional and regional variation. A reference clause may have national forks, regional forks, community-specific forks, sectoral forks, or emergency forks. Each fork should retain parent lineage, divergence reason, scope, changed logic, recognition status, compatibility warnings, and supersession links. This allows future reviewers to distinguish between a global reference rule, a national implementation, a regional adaptation, and a temporary emergency modification. This is how NSF prevents policy amnesia. Rules do not disappear when updated. They become part of a living governance history tree. ### Clause-Attested Records as Time-Indexed Evidence Clause-Attested Compute records, proof receipts, and clause-attested records are not only present-time verification artifacts. They are time-indexed evidence records. They allow future reviewers to understand how a rule was applied at a specific time under specific conditions. A time-resilient clause-attested record should identify the exact clause version, jurisdictional fork, source authority, input evidence, input data classifications, compute environment, model version where relevant, actor identity, credential state, timestamp, result, uncertainty, output status, proof scope, public-safe classification, and correction path. If a credential was issued, suspended, renewed, or revoked, the record should identify the credential hash or identifier, credential schema, issuer, subject class, status, and revocation pathway. If a simulation was used, the record should link to the simulation package. If the output was public-facing, the record should link to the public-safe transformation logic. These records answer temporal accountability questions. Did the system apply the same logic last year? Which version governed a given output? Was a credential revoked under an active clause or a superseded one? Did a model produce false positives during a specific time window? Was a disaster readiness signal generated before or after a threshold update? Was a public-safe map based on corrected data or stale data? Did a Project SPV maturity record depend on a clause later found to be flawed? The record should also indicate current status. A past record may remain historically valid as evidence of what occurred while also being marked as corrected, superseded, disputed, revoked, restricted, or stale. This distinction is vital. Historical records should not be erased simply because they are later corrected. But neither should they continue to be treated as current without status. Together, clause histories and clause-attested records create verifiability of action across time. They allow institutions to inspect not only what a system says now, but what it did then. ### Preservation Without Centralized Trust Time-resilient governance cannot depend on a single institution, platform, vendor, cloud provider, or political authority remaining stable forever. Institutions may reorganize. Governments may change. Regional arrangements may evolve. Vendors may exit. Platforms may be deprecated. Conflicts, disasters, cyberattacks, budget cuts, legal reforms, or geopolitical events may disrupt record systems. The Nexus Sovereignty Framework therefore requires preservation without centralized trust. This does not mean uncontrolled public replication of all data. Sensitive records, personal data, community knowledge, health data, critical infrastructure telemetry, protected-source material, Project SPV evidence, and sovereign-sensitive information must remain protected. Preservation must be designed through access tiers, encryption, redaction, metadata minimization, Sovereign Data Zones, controlled rooms, and public-safe archiving. The principle is distributed survivability with governed disclosure. Clause histories, proof receipt hashes, credential status records, public-safe summaries, schema definitions, version metadata, and correction states may be anchored across federated registries. These may include national registries, Regional Nexus Consortium registries, global reference registries, public-good archives, academic archives, scientific repositories, multilateral evidence environments, civil society observatories, offline archives, and physically resilient backup media. Sensitive underlying data may remain inside sovereign, institutional, community, or controlled repositories, while integrity proofs, metadata, and status references are preserved in broader networks. A national registry may preserve domestic clause forks and public authority references. A regional registry may preserve treaty-aware or corridor-specific clause profiles. A global reference registry may preserve interoperability schemas and reference versions. An academic archive may preserve simulation packages. A civil society node may preserve public-safe reports and correction notices. A cold archive may preserve disaster recovery copies. A distributed content-addressed system may preserve non-sensitive artifacts and hashes. A sovereign archive may preserve restricted records under local control. No single repository should be treated as the only memory of governance. The record fabric should survive institutional change by preserving enough distributed, signed, status-aware, and access-controlled evidence to reconstruct meaning. The goal is not radical transparency. The goal is durable accountability. ### Simulation as Long-Term Foresight Memory In NSF, simulations are not disposable analytical exercises. They are long-term foresight artifacts. Every significant clause adoption, upgrade, fork, public-safe output rule, AI control, disaster trigger, finance-readiness profile, or infrastructure resilience standard should preserve the simulation records that supported it. A simulation package should include baseline data references, model identity, model version, assumptions, parameter values, spatial scope, temporal scope, scenario design, synthetic data labels, historical comparison, risk assumptions, stress conditions, validation method, failure modes, uncertainty ranges, reviewer records, public-safe limitations, and correction status. It should also state what the simulation was intended to test and what it did not test. This allows future reinterpretation. A climate adaptation clause designed in 2026 for sea-level rise can be rerun in 2040 with updated ocean data, storm surge records, subsidence measurements, infrastructure performance, and improved climate models. A supply-chain resilience clause simulated for 2027 trade volumes can be retested after a major port disruption, conflict, pandemic, or energy shock. A vaccine logistics clause upgraded in 2029 can be reverse-analyzed in 2050 to understand whether the assumptions, equity constraints, cold-chain records, and public health thresholds were appropriate. A drought finance-readiness clause can be compared against later rainfall, crop yield, food price, migration, and vulnerability outcomes. An AI model governance clause can be re-evaluated after later evidence of model drift, tool misuse, or incident patterns. Simulation as memory supports accountability and learning. It shows not only what institutions believed, but what they tested. It reveals known risks, ignored risks, uncertainty ranges, and assumptions that later proved right or wrong. It allows future actors to distinguish negligence from reasonable uncertainty, and foresight from hindsight. A governance system that preserves decisions but not simulations preserves outcomes without reasoning. NSF must preserve both. ### Governance Continuity Through Councils, Quorums, and Stewardship Records The original DAO-centric language should be replaced with a more institutionally credible model: councils, validator quorums, controlled rooms, registries, stewardship records, contribution histories, and role-bound governance logs. DAO tooling may be used where useful, but it should not be the constitutional foundation of NSF for public-sector, multilateral, sovereign, or community-facing contexts. Governance continuity requires preservation of who participated, under what authority, with which credentials, in which role, under which conflict-of-interest conditions, with what quorum, with what dissent, with what evidence, and with what decision result. These records should include voter or reviewer credential status where applicable, institutional role, contribution history, domain scope, review materials, simulation acceptance or rejection, fork decisions, dispute histories, and correction decisions. A council record may show that a national clause fork was reviewed by a public authority, a technical institute, community representatives, and domain experts. A validator quorum record may show that a proof receipt schema was accepted under a defined assurance profile. A controlled-room record may show that sensitive evidence was reviewed without public disclosure. A dispute record may show that a credential revocation was challenged and later corrected. A stewardship record may show that a public-safe reporting rule was modified after community concerns. These records preserve governance context. They allow future actors to understand whether a decision had appropriate review, whether conflicts were disclosed, whether dissent existed, whether a minority concern later proved important, whether a decision was rushed, whether an emergency exception was used, and whether correction followed. This is especially important during contested transitions. If an institution loses legitimacy, a government changes, a region reorganizes, a conflict disrupts records, or a system migrates platforms, governance continuity records help restore trust. They show how rules were made and who carried responsibility at the time. Governance continuity is not merely technical. It is the preservation of institutional accountability across time. ### Governance Without Temporal Discretion Many governance systems allow rules, records, and decisions to disappear without a trace. A policy may be overwritten. A database may be migrated. A web page may vanish. A version may be lost. A certificate may be revoked without a clear evidence record. A model may be updated without retaining the prior version. A public dashboard may change methodology without explanation. A project record may be edited after controversy. A data-sharing agreement may expire without preserving the operational conditions under which data was used. The Nexus Sovereignty Framework rejects discretionary disappearance for material governance records. No clause should be deleted when it is no longer active. It should be deprecated, superseded, restricted, or archived with status. No credential should be revoked without issuer identity, authority scope, status reason, record link, and correction path. No policy should be forked without lineage metadata. No material upgrade should occur without version history and review record. No public-safe output should be modified without preserving correction history. No model-governed decision should lose the model version or input context that produced it. No Project SPV evidence record should be silently edited without trace. This does not mean everything must be publicly visible forever. Privacy, safety, legal protection, community safeguards, national security, and data protection may require restrictions, redaction, deletion of raw data, or controlled access. The key is that governance meaning should not be secretly overwritten. Where data must be deleted, a deletion proof, retention basis, lawful reason, or status record may be preserved without exposing the deleted content. Where sensitive material cannot be public, a restricted record can preserve existence, status, and correction metadata under proper controls. The principle is verifiable change. Truth is not frozen, but change must be traceable. Records are not immutable for ideology. They are preserved so that change remains accountable. In NSF, history is not an obstacle to upgrade. It is what makes upgrade trustworthy. ### Multi-Generation Credentialing Credentialing systems are often designed for short-term verification: valid, expired, revoked, or unknown. But many credentials have long-term significance. Land tenure, educational qualifications, professional licensing, public service eligibility, aviation experience, medical records, community rights, infrastructure maintenance, environmental safeguards, biodiversity offsets, carbon projects, insurance exposure records, development finance evidence, and Project SPV governance documents may need to remain verifiable across decades. The Nexus Sovereignty Framework treats credentials as temporal, relational, and status-aware records. A credential should carry issuer identity, subject identity, evidence basis, clause link, proof receipt link, issuance time, validity period, scope, renewal logic, revocation conditions, dispute status, delegation rules, successor logic, and correction history. Multi-generation credentialing requires interoperability over time. W3C-compatible verifiable credentials, decentralized identifiers, selective disclosure, status lists, cryptographic agility, post-quantum readiness, schema migration, archival signatures, revocation registries, and issuer succession records may all be necessary. A credential issued today should not become unverifiable simply because an institution changed name, migrated systems, updated cryptography, or reorganized authority. Land tenure credentials may need to remain intelligible across decades of political, administrative, and technical change. Aviation licensing records may need to preserve training, medical, and operational history across a professional lifetime. Biodiversity offset records may require monitoring, dispute, restoration, and performance records for twenty-five years or more. Community knowledge permissions may need to preserve consent conditions, access limits, attribution preferences, withdrawal rights, and public-safe boundaries. Infrastructure maintenance credentials may need to survive asset transfer, refinancing, insurance renewal, or disaster review. This requires successor functions. If an issuing authority is reorganized, the successor authority should be linked. If a credential schema is upgraded, old credentials should remain interpretable. If cryptographic methods become weak, migration paths should preserve validity without erasing history. If a credential is disputed, the dispute should be status-visible. If revocation occurs, the reason and authority should be recorded. Credentialing is no longer a static act. It is a temporal relationship between issuer, subject, evidence, authority, and future verification. ### Time-Resilient Governance Interoperability As institutions interact over decades, they require interoperability not only across space, but across time. A national system built in 2028 may need to interoperate with a regional system upgraded in 2035 and a global reference framework revised in 2042. A credential issued under one schema may need to be interpreted under a successor schema. A treaty-aligned clause may need to be compared across states whose national forks evolved differently. A digital twin state may need to be replayed using archived model metadata. A public-safe report may need to be interpreted after disclosure standards have changed. Time-resilient interoperability requires protocol-level continuity. Records must preserve semantic meaning, schema version, source authority, jurisdiction, status, dependencies, and migration paths. A future system must be able to understand not only the data format, but the governance context. Semantic traceability is central. A term used in one version of a clause may be replaced in another. A risk category may be reclassified. A public health threshold may be updated. A climate scenario may be superseded. A credential status term may change. A geospatial resolution rule may be revised. Without semantic mapping, old records become unreadable or misleading. NSF should therefore maintain semantic versioning, ontology mappings, schema migration records, deprecation notices, compatibility warnings, and translation profiles. If a record is migrated, the migration itself should be recorded. If a historical term is mapped to a modern term, the mapping should state whether it is exact, approximate, partial, or deprecated. If a clause from a prior jurisdiction is interpreted by a successor state or regional body, lineage and recognition status should be visible. This supports governance after disruption. If conflict, disaster, institutional collapse, or platform failure disrupts records, a time-resilient NSF environment should help rebuild governance history. It should allow successor institutions, public authorities, communities, auditors, courts, technical reviewers, and historians to reconstruct enough of the record fabric to restore legitimacy. Interoperability across time is the foundation of intergenerational trust. ### Archival Architecture and Cryptographic Agility Intergenerational verifiability requires an archival architecture that can survive technological change. Cryptographic algorithms age. Hash functions can weaken. Signature schemes can become obsolete. File formats can disappear. APIs can change. Hardware can fail. Cloud providers can exit. Storage media can degrade. Quantum-adjacent risks may require migration to post-quantum cryptography. A record architecture that assumes today’s cryptography and storage methods will remain sufficient forever is not time-resilient. The Nexus Sovereignty Framework must therefore include cryptographic agility and archival migration. Records should support algorithm identifiers, signature timestamps, certificate chains, key status, revocation, re-signing, hash migration, post-quantum transition paths, and archival proof renewal. If an old hash function is deprecated, the system should preserve the old hash for historical continuity while anchoring the record under a stronger method. If a signature scheme becomes weak, records may need re-attestation by authorized archival processes. If a credential issuer rotates keys, key history should remain verifiable. If a ledger becomes obsolete, proof anchors should be migratable. Archival formats should favor openness, documentation, and long-term readability. Critical records should not exist only inside proprietary databases or closed platform exports. Where sensitive content cannot be publicly archived, metadata and proof records should preserve enough structure to support future verification under controlled access. Physical resilience also matters. Offline archives, cold storage, national archives, academic repositories, public-good archives, regional backups, printed or physical media for critical hashes, and disaster recovery procedures may all be necessary for high-value governance records. Digital resilience should not assume permanent connectivity. A time-resilient system must be able to say: even if technology changes, even if keys rotate, even if algorithms age, even if platforms disappear, the record can still be interpreted and its integrity can still be evaluated. ### Time-Resilient AI, Models, and Digital Twins AI systems and digital twins create special temporal risks. Models change. Training data changes. Retrieval systems change. Embeddings change. Prompts change. Tools change. Simulation environments change. A model output produced today may be impossible to interpret tomorrow if the model version, data context, prompt, parameters, retrieval sources, tool calls, or guardrails are not preserved. NSF should require time-resilient model records for high-consequence AI use. A model-governed decision-support record should identify the model, version, provider or host, deployment context, input class, prompt or instruction profile where appropriate, retrieval sources, tool calls, guardrails, evaluation state, human review status, output classification, and correction path. If a model is retired, dependent records should remain interpretable. If a model is found to have a bias, vulnerability, hallucination pattern, or security issue, affected historical records should be flaggable. Digital twins require similar discipline. A digital twin state should preserve data sources, spatial scope, temporal scope, model assumptions, asset states, hazard layers, uncertainty, simulation outputs, public-safe transformations, and version history. If a city, watershed, port, grid, hospital, corridor, or Project SPV is represented through a digital twin, future reviewers must be able to reconstruct which twin state informed which decision or record. This matters for accountability. A disaster model may influence evacuation planning. A flood simulation may influence infrastructure finance-readiness. An AI maintenance model may influence critical infrastructure operations. A public health model may influence service allocation. A digital twin may influence land-use planning. Without temporal records, future actors cannot know whether the system acted reasonably under the evidence available at the time. Time-resilient AI governance ensures that models do not erase their own past. ### Public-Safe Memory and the Right to Correction Intergenerational verifiability must be balanced with privacy, safety, community safeguards, and correction. Preservation must not become permanent exposure. A governance system that keeps everything forever without access controls can create harm. Personal data, protected health information, community knowledge, Indigenous data, critical infrastructure details, humanitarian protection data, security-sensitive records, and market-sensitive evidence require careful handling. NSF must therefore distinguish between preserving governance meaning and exposing raw content. A record may preserve that a check occurred without preserving sensitive raw data. A proof receipt may remain visible while the underlying data remains restricted or deleted under retention law. A public-safe summary may remain accessible while controlled-room evidence remains protected. A correction notice may show that an output was superseded without revealing protected details. The right to correction is essential. If a record is wrong, harmful, outdated, or improperly disclosed, the system must support correction, annotation, restriction, revocation, or withdrawal. Historical preservation should not become an excuse for immutable error. NSF’s doctrine is correctionability, not permanent infallibility. This is especially important for communities. Local and Indigenous knowledge may be shared under specific conditions, for specific purposes, or through specific stewards. Intergenerational records must respect those conditions. Public-safe memory should allow future accountability without turning sensitive knowledge into permanent open data. A mature NSF archive must therefore be access-tiered, rights-aware, correctionable, and public-safe. ### NSF as a Trust Layer for Intergenerational Resilience The true test of a governance protocol is not whether it works today. It is whether it can still be inspected, explained, simulated, corrected, and restored a generation from now under new institutions, technologies, risks, and political conditions. A system that passes today’s compliance audit may still fail the intergenerational test if its records cannot be interpreted later. A system that matches current law may fail if it cannot preserve the rule history that led to later decisions. A system that runs on modern cloud infrastructure may fail if it cannot migrate without losing audit trails. A system that uses cryptographic proofs may fail if it cannot adapt to new cryptographic risks. A system that produces AI-supported outputs may fail if future reviewers cannot reconstruct the model context. A system that issues credentials may fail if issuer succession, revocation, and schema migration are not preserved. A system that supports public-safe reporting may fail if corrections cannot propagate. The Nexus Sovereignty Framework is designed to answer yes to the intergenerational test. It does so by making verifiability temporal, not merely transactional. Clauses are versioned. Proof receipts are time-indexed. Credentials are status-aware. Simulations are preserved as foresight memory. Registries are federated. Governance records preserve participation and dissent. Archives are cryptographically agile. AI and digital twin outputs preserve lineage. Public-safe memory protects sensitive content while preserving accountability. Corrections remain part of the record. This is the foundation of intergenerational resilience. It allows member states, regional bodies, UN-level institutions, development banks, insurers, investors, communities, public authorities, technical operators, and future generations to inspect the governance systems that shaped them. Verifiability is not a feature added to governance. In NSF, verifiability is the condition of legitimacy across time. The Framework must therefore be built not only for present trust, but for future restoration. It must allow institutions to survive disruption, recover memory, compare versions, rerun simulations, migrate credentials, correct errors, and preserve sovereignty through technological change. That is intergenerational verifiability in the Nexus Sovereignty Framework: governance designed to remain trustworthy beyond the generation that created it. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.therisk.global/organization/standardization/nexus-sovereignty/i.-foundations/intergenerational-verifiability-and-protocol-longevity.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.