# 5.5 Integrity ### **5.5 Correction, Supersession, and Historical-Integrity Chain** #### **5.5.1 Why correction is part of system motion rather than editorial cleanup** A system of the kind proposed in this Whitepaper cannot treat correction as a marginal, embarrassing, or purely editorial activity. In the Nexus Ecosystem, correction is part of the operating architecture of trust. It is one of the ways the system remains credible under pressure, complexity, localization, growth, and scrutiny. A category that claims to connect sovereign compute, observability, institutional validity, standards activation, routeability, host deployment, public-purpose relevance, and long-horizon lifecycle stewardship cannot rely on a naïve model of truth in which the first published or first recorded version is assumed to remain sufficient merely because it was once properly assembled. Such a model fails under real-world conditions. Evidence changes. Hosts change. dependencies are reclassified. standing states evolve. route classes narrow. degraded operation reveals facts not previously visible. public descriptions outrun technical reality. local pathways mature more slowly or more quickly than anticipated. In such an environment, correction is not an admission of weakness. It is the disciplined means by which the system preserves coherence while reality continues to move. This is why the architecture treats correction as a **movement discipline**, not a cosmetic patch. A correction changes more than wording. It changes how the chain must be read from that point onward. It may affect standing, comparability, routeability, maturity interpretation, host suitability, public claims, derivative lineage, or downstream reliance posture. If handled weakly, a correction can produce fragmentation, because some parts of the ecosystem continue operating on obsolete assumptions while others move ahead. If handled strongly, correction preserves a single history across multiple layers, jurisdictions, and actor classes. The distinction between editorial cleanup and system correction is therefore decisive. a) **Editorial cleanup** concerns clarity of expression, typographic precision, stylistic consistency, or other matters whose improvement does not alter the meaning, class, reliance posture, or force of the underlying artifact. b) **System correction** concerns changes in meaning, scope, truth value, standing implication, maturity interpretation, dependency logic, routeability posture, supportability reality, or public-description consequence. c) **Historical-integrity correction** concerns the preservation of continuity between prior and current understanding, so that the chain does not conceal how meaning changed or who relied on what, when. d) **Governance-relevant correction** concerns adjustments whose effect reaches beyond a single document and into status, responsibilities, thresholds, or downstream interpretive behavior. The Whitepaper must therefore proceed from a clear rule: the Nexus Ecosystem is not serious because it is unchanging. It is serious because it is **correctable without losing continuity of meaning**. This is one of the decisive ways in which it differs from shallow ecosystem narratives. Those models often seek legitimacy by projecting permanence. Nexus seeks legitimacy by combining disciplined structure with disciplined revision. That posture is stronger, not weaker, because it allows the system to absorb reality without surrendering architectural identity. This point also has direct relevance to sovereign compute initiatives and associated public-purpose programs. In this domain, the cost of uncorrected error is unusually high. A mistaken host classification may distort support planning. A stale lifecycle assumption may produce false reserve logic. An outdated routeability interpretation may mislead external readers into believing downstream readiness is stronger than it is. A public-safe summary that is not corrected after a technical downgrade may continue to shape ministerial, donor, investor, or host expectations long after its basis has weakened. The architecture cannot allow such divergence. Correction must therefore be built into the movement of the chain itself. The final reason correction must be treated as system motion is that Part V is not only describing artifacts. It is describing the choreography of a distributed global ecosystem. In a distributed system, delay in correction is itself a meaningful fact. The challenge is not simply to notice an error. It is to ensure that the corrected meaning propagates across global, regional, national, host, industrial, standards, capital-interface, and public-description layers with enough discipline that the ecosystem remains one chain rather than many partially updated chains. That is why correction belongs here, in Part V, as a whole-of-chain movement function. *** #### **5.5.2 What enters the correction chain** Not everything in the ecosystem enters the correction chain in the same way, but anything that can alter the truth, meaning, reliance posture, or historical reading of the chain must be understood as potentially correction-bearing. The correction chain is therefore broader than document revision and narrower than general change management. It is the disciplined channel through which the system handles meaning-bearing changes whose effects matter beyond a single local context. The following classes of matter may enter the correction chain. a) **Evidence-bearing artifacts**, including assurance and evidence packs, verification annexes, observability outputs, risk and readiness assessments, host evaluation materials, routeability dossiers, and other structured objects whose meaning may later be refined, narrowed, challenged, or superseded. b) **Standing-relevant artifacts and states**, including recognition status, admissibility posture, qualification classes, conformance-bearing descriptions, participant standing, host standing, route-class posture, and maturity descriptors that may later require narrowing, downgrade, restoration, or clarification. c) **Technical and lifecycle artifacts**, including class definitions, configuration truth, profile applicability, service records, refresh states, trust restoration records, and runtime-behavior descriptions when these affect how the estate should be interpreted or relied upon. d) **Institutional and governance artifacts**, including designated acts, records-valid decisions, derivative documents, schedule or annex linkages, official summaries, pathway classifications, support designations, or other artifacts that influence who carries what burden or how the chain is meant to move. e) **Public-description artifacts**, including public-safe summaries, external descriptions, partner-facing statements, investor-facing materials, host-facing overviews, and other derivative communications whose meaning must remain aligned to the strongest authoritative source. f) **Cross-layer mappings and comparative views**, including dashboards, status matrices, maturity tables, geographic maps, burden maps, route maps, or chain maps, because these can powerfully shape interpretation even when they are not themselves force-bearing. These broad classes should not be read as though every item in them is always subject to the same correction regime. Rather, they show the kinds of matter that may become correction-relevant if new evidence emerges, if interpretation changes, if profile or host context narrows, if routeability weakens, if support assumptions prove false, or if public description drifts beyond source truth. What enters the correction chain, then, is not merely “anything that changed.” It is anything whose change matters to the continuing integrity of the chain. To make that principle operational, the correction chain should be read through four filtering questions. a) **Does the matter affect meaning?**\ If the answer is no, the issue may remain editorial. If yes, correction discipline may be engaged. b) **Does the matter affect reliance or interpretation?**\ If readers, hosts, institutions, public authorities, or downstream actors would think differently about the object after the change, the issue is likely correction-bearing. c) **Does the matter affect position in the chain?**\ If a matter changes whether something is merely descriptive, standing-relevant, routeability-relevant, downgraded, restored, or superseded, then the correction chain is implicated. d) **Does the matter affect lineage?**\ If the historical relationship between earlier and later artifacts must be preserved to prevent confusion, then the matter belongs in the correction chain even if outward wording changes appear small. This approach is essential because the Nexus Ecosystem will produce many artifacts at many levels. Some will be experimental. Some will be transitional. Some will be public-safe. Some will be highly structured and threshold-bearing. The correction chain is the mechanism that allows these artifacts to continue existing in a common governed memory even when their meaning changes over time. That is how the ecosystem avoids both silent edits and frozen error. *** #### **5.5.3 Trigger classes for correction, contest, and supersession** A mature correction system does not wait until institutional embarrassment becomes obvious. It defines **trigger classes** that indicate when correction, contest, clarification, narrowing, or supersession must be considered. In Nexus, trigger classes are essential because the ecosystem includes many layers of movement and many actor classes. Without formal triggers, some corrections would occur only where the most disciplined teams happen to notice them, while other areas of the chain would continue operating on outdated or overstated assumptions. Trigger classes can be organized into three principal bands: **correction triggers**, **contest triggers**, and **supersession triggers**. **a) Correction triggers** These arise where the chain’s current representation remains broadly in the right class but contains material inaccuracy, incompleteness, overstatement, scope ambiguity, stale dependency logic, or contextual error that must be remedied to preserve truthful interpretation. Examples include: i) evidence updates that alter conclusions without fully displacing the underlying object;\ ii) host-condition changes that narrow what an earlier assessment can safely support;\ iii) service or lifecycle events that alter the current status of a previously admitted class;\ iv) newly visible dependency or trust-surface facts that require restatement of posture;\ v) maturity language that is now too strong for the actual state of the chain;\ vi) public-safe summaries whose continuing wording no longer matches the underlying source. **b) Contest triggers** These arise where the existing meaning is challenged by another actor, another body of evidence, another layer of the ecosystem, or another lawful interpretation pathway. Contest does not automatically imply error, but it does require structured handling. Examples include: i) disputes over standing or routeability interpretation;\ ii) conflicts between host reality and regional or global descriptive posture;\ iii) divergence between technical-state evidence and governance summaries;\ iv) objections from participants, hosts, local communities, or public authorities regarding how a matter has been described or classified;\ v) competing interpretations of derivative narrowing or profile applicability. **c) Supersession triggers** These arise where the older object, posture, or description remains historically significant but is no longer the correct current basis for interpretation, use, or reliance. Supersession is not deletion. It is ordered replacement with preserved lineage. Examples include: i) new versions of force-bearing or standing-relevant artifacts;\ ii) major routeability changes that alter the relevant pathway logic;\ iii) redesignation of host class, maturity state, or support posture;\ iv) structural changes in architecture, systems family, or derivative hierarchy that displace prior formulations;\ v) replacement of interim hosted arrangements by locally grounded self-carrying states. These trigger classes should not be treated as mutually exclusive. A matter may begin as a contest trigger, become a correction matter during review, and end in supersession if the new interpretation materially displaces the old one. The point of the classification is not to force clean categories for their own sake, but to provide discipline and pace. The existence of trigger classes also helps protect against two distortions. a) It prevents **hypercorrection**, in which every minor variation is treated as though it threatens architectural integrity. b) It prevents **correction avoidance**, in which high-consequence changes are delayed because teams are uncertain whether the matter is “serious enough” to justify formal action. A good correction regime is neither timid nor frantic. It is proportional. Trigger classes are what make proportionality possible. *** #### **5.5.4 Local correction propagation** Local correction propagation concerns the first zone in which updated meaning must move: the immediate site, host, pathway, runtime, service, or artifact context in which the issue was detected or from which the correction meaning first arises. In many systems, local correction is treated as simple patching. In Nexus, it must be treated as the first stage of historical and interpretive containment. If a local matter is corrected without disciplined propagation even at the local level, the ecosystem begins producing parallel truths: the corrected truth and the lingering operational memory of the earlier state. Local correction propagation therefore has several duties. a) **Immediate containment of interpretive drift**, so that local operators, hosts, support teams, or pathway actors stop relying on the outdated or overstated meaning as soon as practical. b) **Update of local source artifacts**, so that the corrected state is visible in the authoritative object and not merely communicated informally. c) **Preservation of local lineage**, so that users can still determine what the prior meaning was, why it changed, and from what date or trigger the correction became active. d) **Adjustment of local derivative materials**, including summaries, dashboards, host notes, or route descriptions whose continued use could perpetuate error. e) **Preparation of escalation bundles**, where the matter has effects beyond the immediate local setting and must be carried to regional, national, or global layers. The local layer is especially important because it is the point at which truth is often closest to operational reality. Hosts, support teams, and local institutions frequently see degradation, mismatch, service strain, contextual misfit, or overstated assumptions before those conditions are fully legible at higher levels. A mature correction regime must therefore respect local visibility without allowing local correction to become local rewriting. Local correction does not authorize local doctrinal reinvention. It authorizes disciplined updating of local truth within the common chain. This means local propagation must follow several constraints. a) It may narrow, clarify, or update the local posture.\ b) It may not silently widen local authority or alter the common baseline.\ c) It must preserve linkage to the stronger upstream source and derivative hierarchy.\ d) It must escalate where the matter materially affects standing, routeability, public description, or cross-jurisdictional comparability.\ e) It must distinguish between immediate local operational mitigation and the fuller documentary correction that preserves long-horizon chain truth. Done properly, local correction propagation increases trust. It shows that the system can respond where reality is first visible while still remaining one governed architecture. Done badly, it becomes the first point of fork behavior. That is why local correction must be disciplined, visible, and lineage-preserving from the start. *** #### **5.5.5 Regional correction propagation** Regional correction propagation exists because the chain is not purely local and not purely global. The regional layer serves as a comparability, support, coordination, continuity, and translation surface. When a correction has effects broader than one host or one localized pathway, but narrower than an immediate system-wide doctrinal rewrite, the regional layer becomes the crucial intermediary through which the ecosystem remains coherent without over-centralizing every update. Regional correction propagation typically becomes necessary where a change affects: a) multiple countries within a region;\ b) a shared route class or support pattern;\ c) regional burden allocation or continuity assumptions;\ d) host archetypes that recur across the region;\ e) comparative dashboards, support notes, or readiness interpretations used regionally; or\ f) regional public-facing or partner-facing descriptions that would become misleading if local correction were not lifted upward. Its tasks are therefore different from local correction. The regional layer must: a) determine whether the matter is region-specific, region-amplified, or merely region-notifiable;\ b) assess whether other national or host pathways are exposed to the same issue;\ c) update shared regional summaries, comparative views, and support assumptions;\ d) ensure that similar pathways are not left operating under stale interpretations;\ e) decide whether escalation to the global layer is required because the matter affects common doctrine, common public description, or cross-regional comparability. Regional propagation is especially important in an ecosystem like Nexus because support-without-control must remain real. A strong regional layer should help absorb and transmit correction without becoming a hidden authority that rewrites national truth. That means regional correction must remain: a) **amplifying**, where broader visibility is required;\ b) **harmonizing**, where comparability would otherwise break;\ c) **supportive**, where less mature national pathways need help interpreting the effect of a change; and\ d) **bounded**, where the region must not displace the locally grounded truth or silently elevate itself into the primary source of meaning. The regional layer is also often the place where correction begins to affect strategic narrative. A local issue may reveal that an entire regional host pattern was being described too strongly, that support burdens are more concentrated than previously assumed, that a telecom-integrated route class has weaker comparability than earlier summaries suggested, or that a continuity assumption across several countries needs to be revised. Those are not merely local matters, but they are also not always global crises. The regional layer is therefore a necessary correction mediator. This mediation function is one of the reasons Part VII later becomes so important. But here in Part V, the rule is enough: where local correction affects regional comparability, support patterns, maturity interpretation, or public-description coherence, regional propagation is mandatory. *** #### **5.5.6 Global correction propagation** Global correction propagation is required where a matter affects the common architecture, the common chain of meaning, the public understanding of the category, the relationship among derivatives, or the truthful basis on which different regions and national pathways are being compared. It is the strongest level of correction not because it overrides local or regional truth, but because it preserves coherence across the system as a whole. Global propagation is engaged where a correction reaches one or more of the following thresholds. a) It affects a common baseline, common systems-family description, common routeability understanding, common profile logic, common standing interpretation, or another architecture-wide formulation. b) It affects multiple regions such that regional propagation alone would leave the wider ecosystem with inconsistent understandings of the same class, state, or object. c) It affects public-safe descriptions of the category at global level, including how the ecosystem is described to sovereigns, development partners, industrial actors, capital-facing readers, or the wider public. d) It affects derivative lineage such that regional, national, host, or sectoral derivatives would otherwise continue narrowing from a source that is no longer current. e) It affects the historical integrity of the system, such that a major claim, designation, threshold, or interpretation must be formally preserved as superseded rather than left to drift into informal replacement. Global propagation has three major purposes. a) **Coherence preservation**: ensuring that the system remains one architecture despite the fact that corrections may originate locally or regionally. b) **Historical stabilization**: making clear not only what is now true, but what was previously held to be true and how that position changed. c) **Claims discipline**: ensuring that the strongest outward-facing descriptions remain subordinate to the strongest current source rather than to narrative lag. The global layer must, however, exercise this function with discipline. It must not universalize local correction where the matter is genuinely local. It must not erase local or regional specificity in the name of tidiness. And it must not overreact by transforming every meaningful update into a doctrine-level revision. The point of global propagation is not maximal centralization. It is maximal chain coherence where the correction genuinely affects common meaning. A well-run global propagation regime therefore does three things at once: a) it preserves the **common rail**;\ b) it respects **local grounding and regional mediation**; and\ c) it prevents **global narrative lag**, which is one of the most dangerous forms of maturity inflation in internationally visible systems. In the Nexus Ecosystem, this discipline is especially important because public and strategic audiences may encounter the category first through global summaries, executive propositions, and institutional descriptions rather than through local technical artifacts. If those materials fail to reflect major corrections in the chain, the ecosystem will begin producing contradictory truths at different altitudes of visibility. That failure cannot be permitted in a category that seeks sovereign, institutional, and global seriousness. *** #### **5.5.7 Effect of correction on standing, comparability, routeability, and public claims** Correction is not merely an update to content. It has effects. Those effects must be explicitly governed because different kinds of correction alter different parts of the chain. Some corrections are narrow and local. Others ripple into standing, comparability, routeability, and public-description consequences. The architecture must therefore be explicit about what a correction may change and how those changes are recognized. **a) Effect on standing** A correction may leave standing unaffected, clarify it, narrow it, suspend it, downgrade it, or later support its restoration. The key point is that standing cannot be assumed to remain intact merely because the underlying artifact still exists. If a correction materially changes the truth on which standing depended, then the standing posture may need to be re-read. This does not mean every correction should trigger a standing review, but it does mean that standing must remain conditionally tethered to corrected meaning rather than insulated from it. **b) Effect on comparability** Comparability is especially sensitive to correction because it depends on stable interpretation across jurisdictions, hosts, pathways, and actor classes. A local correction that reveals a classification inconsistency, a profile mismatch, a host-assumption weakness, or an overstated maturity descriptor may weaken prior comparisons that relied on the older interpretation. In such cases, the ecosystem must decide whether comparability can be preserved by annotation, whether it must be narrowed, or whether the previous comparison set is no longer safe. The cost of ignoring this question is high: misleading comparisons can influence sovereign, partner, donor, and capital-facing judgments long after the underlying basis has weakened. **c) Effect on routeability** Routeability is particularly vulnerable to correction because it often sits near external consequence. If a correction alters proof sufficiency, host readiness, supportability, route-class fit, derivative lineage, public-authority assumptions, or unresolved dependency posture, then the routeability state may need to change. This may mean: i) reaffirmation with updated conditions;\ ii) narrowing of route type or counterpart class;\ iii) pause pending additional validation;\ iv) downgrade to a weaker readiness posture; or\ v) full supersession of the prior routeability interpretation. The system must be disciplined here. A corrected routeability state is not a reputational insult; it is a truthful restatement of where the chain stands. **d) Effect on public claims** Public claims must remain among the first things affected by correction, not the last. It is precisely because public-safe materials are derivative and audience-facing that they must be updated when corrected truth changes the proper description of maturity, standing, comparability, local ownership, routeability, internationalization, or host readiness. Public claims cannot be allowed to trail behind source truth simply because they are convenient, widely circulated, or rhetorically effective. In the Nexus model, public-description lag is itself a governance problem. The broader principle is therefore clear: corrections must have visible consequence where the meaning of the chain changes. A correction regime that updates only the underlying object but leaves standing, comparability, routeability, and public narrative untouched is not preserving integrity. It is merely relocating inconsistency. *** #### **5.5.8 Historical retention, supersession lineage, and audit memory** A correction-rich ecosystem can remain trustworthy only if it preserves historical retention, clear supersession lineage, and strong audit memory. These are not archival luxuries. They are part of the architecture’s truth-preserving capacity. The system must be able to answer not only, “What is the current position?” but also, “What was previously held to be true, by whom, in what class, and how did the system move from that prior posture to the current one?” That is what makes the chain challengeable, governable, and historically honest. **a) Historical retention** Historical retention means that prior artifacts, states, summaries, and designations are not silently erased simply because they are no longer current. They remain visible in the record with appropriate classification, bounded current reliance, and linkage to later corrections or supersessions. This is essential for institutional memory, review, accountability, and learning. **b) Supersession lineage** Supersession lineage means that the chain must clearly show which artifact or state replaced which prior artifact or state, through what trigger, at what time, and with what change in meaning. Supersession is stronger than amendment because it displaces the current interpretive center while preserving lineage. It is weaker than deletion because it does not pretend the prior object never existed. **c) Audit memory** Audit memory means that the system preserves enough trace to reconstruct why a matter looked the way it did at each stage. This includes not only final outputs but also state transitions, review posture, trigger classes, responsible surfaces, and the evolution of public-safe description. Audit memory is especially important in a system like Nexus because later public-purpose or capital-interface consequences may depend on understanding exactly how a pathway matured, paused, narrowed, or re-entered. These three disciplines matter for several reasons. a) They prevent **silent revisionism**, in which the ecosystem becomes tempted to speak as though it had always known what it only later learned. b) They support **learning without denial**, because the system can absorb change without pretending that change never occurred. c) They support **multi-actor coherence**, because different layers and participants can converge on the same historical narrative rather than preserving divergent informal memories. d) They protect **public trust**, because serious external readers increasingly expect to see not only current posture but disciplined change history. e) They support **future-proofing**, because new waves of participants, hosts, regions, and partners can understand the maturation of the category without relying on oral tradition or selective recollection. The architecture should therefore be read as insisting on an active historical memory, not a static archive. Historical retention, supersession lineage, and audit memory are how the chain remains one chain even after many changes. *** #### **5.5.9 Why correctionability preserves trust under growth and stress** Correctionability preserves trust because trust in a distributed, high-consequence ecosystem is not the same as belief in infallibility. In systems operating across multiple jurisdictions, host types, actor classes, route classes, lifecycle states, and public audiences, mistakes, reinterpretations, narrowings, and reclassifications are unavoidable. What matters is not whether change occurs. What matters is whether the system can absorb change without losing coherence, dignity, or comparability. That capacity is what correctionability provides. Under **growth**, correctionability matters because more actors, more deployments, more derivatives, and more public descriptions create more opportunities for divergence. Without a correction system, growth amplifies inconsistency. With a correction system, growth becomes more governable because errors, overruns, or stale assumptions are brought back into one historical and current chain of meaning. Under **stress**, correctionability matters because pressure exposes the difference between rigid systems and resilient systems. Degraded operation, service interruption, public scrutiny, political urgency, industrial bottlenecks, trust-surface issues, dependency shocks, and routeability disappointments are all more likely during stress. A brittle ecosystem reacts by hiding, delaying, or informally reinterpreting. A correctionable ecosystem reacts by narrowing truth where necessary, propagating the new meaning, preserving lineage, and restoring public description to alignment with current reality. This is a stronger form of trust because it is based on disciplined adaptation, not defensive immobility. Correctionability also preserves trust across reader classes. a) For sovereign readers, it signals that the category respects lawful seriousness enough to narrow claims when required.\ b) For industrial readers, it signals that build truth and lifecycle reality matter more than one-time marketing posture.\ c) For standards and assurance readers, it signals that comparability is defended through discipline rather than protected through denial.\ d) For capital-facing and public-purpose readers, it signals that routeability and readiness language are not being used recklessly.\ e) For hosts and communities, it signals that the system can listen, adjust, and preserve local truth without collapsing into fragmentation. Trust in Nexus is therefore not “trust that nothing changes.” It is “trust that change is governed.” Correctionability is the operational form of that promise. *** #### **5.5.10 Final doctrine of correction and historical integrity** The final doctrine of this section is that the Nexus Ecosystem shall be treated as a system whose seriousness depends on its capacity to correct, supersede, retain, and propagate meaning without losing continuity of identity. Correction is not peripheral to the chain. It is one of the chain’s core protective motions. That doctrine yields the following controlling rules. a) Correction shall be treated as a movement discipline, not a cosmetic or editorial afterthought.\ b) Any matter whose change affects meaning, reliance, state, scope, or lineage may enter the correction chain.\ c) Trigger classes for correction, contest, and supersession shall be explicit enough to prevent both underreaction and hyperreaction.\ d) Local correction shall preserve local truth while remaining bounded by common architecture and derivative discipline.\ e) Regional correction shall preserve comparability, support coherence, and non-fragmentation across related pathways.\ f) Global correction shall preserve common meaning where the architecture, narrative, or derivative hierarchy would otherwise diverge.\ g) Corrections shall have visible consequence where standing, comparability, routeability, or public claims depend on the corrected meaning.\ h) Historical retention, supersession lineage, and audit memory shall be preserved so that the chain remains challengeable and historically honest.\ i) Correctionability shall be understood as a trust-preserving capability under both growth and stress.\ j) No serious artifact, state, or outward-facing description shall be allowed to continue claiming stronger current meaning than the corrected chain can support. The strategic consequence of this doctrine is large. It means the Whitepaper is not proposing a fragile, self-flattering ecosystem that must hide change to preserve credibility. It is proposing an ecosystem strong enough to preserve credibility through disciplined change. In a domain as ambitious as sovereign compute-linked infrastructure, routeability, host localization, lifecycle industrialization, and globally scaled public-purpose deployment, that difference is decisive. Correction and historical integrity are not only safeguards against error. They are part of what makes the category worthy of long-horizon trust. --- # Agent Instructions: 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: ``` GET https://docs.therisk.global/organization/acceleration/nexus-compute/v.-whole-of-chain/5.5-integrity.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.